> I suggest we make the following statement on the computer go list, > regarding the use of code from GNU Go: > > The GNU Go developers have no reservations with regard to 1. if the > only code taken from GNU Go is communications code, in particular > the files gtp.c and gtp.h. Likewise we have no reservations about > consulting GNU Go through GTP for the sole purpose of implementing > final_status_list and final_score. Whether we have reservations > about other uses of GNU Go code will be decided on a case by case > basis. > > Neither of these should affect the move generation in any way. That we > should allow the first use is obvious, the second use is good PR. We > might also add use of the board library to this list, but I don't have > a strong opinion whether that is desirable.
There's little to disagree with here. There's an obvious distinction between gtp.[ch] and board.c that board.c is GPL'd. Although that's not relevant to the question of what constitutes a program that is distinct from GNU Go for tournament play, maybe it is best not to mention board.c unless this is pointed out in the same breath. I do believe it is good to encourage GNU Go forks as long as they are developed openly under the GPL. Dan _______________________________________________ gnugo-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnugo-devel
