[computer-go] Collaboration project. Once again

[Ron Goldman]

On Aug 5, 2006, at 7:18 PM, Markus Enzenberger wrote:
> The Go Text Protocol certainly does not qualify for having  
> "intimate semantics of communication". Then there is no problem and  
> I'll leave GoGui's license as it is.

Markus,

You still might consider switching to LGPL if you would be willing to  
let people create a single executable consisting of GoGui and one or  
more engines. LGPL has the advantage of allowing a closer connection  
between the GTP/GUI side and the Go engine. There are probably good  
arguments for keeping a cleaner, pure GTP interface like you now use  
& also for tighter integration: a great general use GUI for a Go  
program that people can plug different engines into.

At the least you might consider adding a Note in your licensing  
explicitly stating that any engine connected to GoGui via GTP is not  
considered a derivative work. I.e. to rework the note used by Linux:

    NOTE! This copyright does *not* cover Go engines that use GoGui
  services by the GTP protocol - this is merely considered normal use
  of GoGui, and does *not* fall under the heading of "derived work".

If everyone working on different engines can build on GoGui that will  
be way better then if they feel they need to duplicate its  
functionality.

-- Ron --