[computer-go] Collaboration project. Once again

[House, Jason J.]

If by "how to start" you mean coming up with a high level design for
the eventual growth/development of a bot, I think you should.  Even if
the discussion goes nowhere (e.g. no general consensus), it will still
have a number of benefits.  Most notably, those who resonate with your
ideas are more likely to join your project.  I firmly believe that by
discussing things in groups, at least a few new/good ideas come out.
By defending your design, you'll create an even better one.

-----Original Message-----
From: computer-go-bounces at computer-go.org
[mailto:computer-go-bounces at computer-go.org] On Behalf Of Mark Boon
Sent: Wednesday, August 02, 2006 5:43 PM
To: computer-go
Subject: Re: [computer-go] Collaboration project. Once again


I don't even know for sure if I'll succeed in persuading others to  
join. I only know that I want to try. The thing with open-source  
projects is that anyone is always free to take it in another  
direction if they choose to do so. If the majority of the  
contributors then choose to follow the new direction then that's  
where it goes. In open-source projects there can be no real boss who  
single-handedly decides everything. But there must be someone who  
starts it, and that's what I intend to do. That it will mean that at  
the start I decide where it will initially go seems natural to me.  
After all it's going to be something that I think I can personally  
later use in a new Go playing program. How else could I even start?  
Should I start an open discussion about how to start making a Go  
program first? I'm afraid that will lead nowhere.