On Tue, Dec 16, 2008 at 11:34 PM, Tom Lieber
On Tue, Dec 16, 2008 at 3:49 PM, Stephen Sinclair
wrote: Anyways, if you think about it, the only actual difference between creating a "community edition", and everyone just making their own git repos and sharing patches on the list, is that the former case has a web page to describe how to do it.
On Tue, Dec 16, 2008 at 8:15 PM, Stephen Sinclair
wrote: Using a central git repo, we can have branches for each feature people want to integrate, and then just give a shout to the ChucK team saying, "hey we did this, it's in branch X, grab the patch if you want." The key thing being that there will be a "mob" branch that anyone can submit patches to without having to ask for permission.
srsly. and with github, you also get the web page. and on the 'network' page you can see everybody's branches.
http://github.com/AllTom/chuck/tree/1.2.1.2
Someone should do it!
Oh cool I guess it's done then. :) I was thinking of maintain a branch called "upstream" that is always synced against the CVS. As far as I know github doesn't support "mob", that's why I was thinking of using git.or.cz. Steve