Re: OpenGo / GNU / GPL Name Confusion

[Jeffrey Greenberg <jeffg@xxxxxxxxxx>]

Fuming,
    I will have this licensing issue resolved enough to release the code by the
    weekend.  Have you already released jago/gnu-go?  Can you wait till I
    finish my move?  8-)

    On a technical level,  please consider the following:

    Currently the OpenGo interface is a C++ compile time interface.  So there
are two
    choices in the short term:
    A. make a version of OpenGo which is based on Java
    B. make a version of OpenGo that is compiler/os independent.

    Choice A seems like a good way to maintain two separate bodies of code:
        I'm against it.
    Choice B would be a better way: less code to maintain plus other benefits.
        I'm thinking along the lines of an IPC abstraction that would hide the
        actual mechanism which might be messages or pipes or shared memory.
        It would require two changes:
            1. creating the "java-side" (or whatever language side)
                ipc mechanism to connect to the engine.
            2. creating an OpenGo player-proxy (C++) that does the ipc out to
                the engine app.

    If people really think Java is absolutely key to software development, then
        this change could be done sooner rather than later.  Fuming, perhaps
        you're the person to do it!

jeffrey


Fuming Wang wrote:
| My understanding was that the GNU project was looking look an new Go
| program for the next generation of GNU GO. I offered JaGo as an candidate,
| and offered to port the OpenGo _interface_ to JaGo/GNU Go. However, if
| the license of OpenGo has conflicts with GPL, this plan would obviously
| be dropped. Either way, there won't be name conflicts.

in response to On Mon, 12 Oct 1998, Jeffrey Greenberg wrote:
> 1. I'm operating under the idea that I'm going to release an infrastructure
> to help in programming go.   (This week...) Now there's jago that is being
> submitted to GNU... but the messages say "OpenGo"... I've already put out
> information on "OpenGo", got a website and documentation using that name,
> it'll be copyright/left with that name, asked Weiman Xiao who coined the name
> if it was ok with him, and I'd rather not go about changing the name at this
> point: SO, can the jago/gnu effort please use another name?

--
Jeffrey Greenberg
Mgr. Aegis Adv. Dev.
Acuson Corp.
www.ultrasound.com
www.acuson.com
650-694-5422