+1. Some extra pro is that for people will be simpler to contribute to core. Just have their branch, make the changes then tell some core team member to look and pull. In plus is quite easy to see what is changed.
On Thu, Jul 16, 2009 at 12:12 PM, Niclas Hedhman <[email protected]> wrote: > Quingyue's question actually brings up the question whether we should > move the codebase to Github?? > > Pros; > + Many people knows how to use it. > + Quite a lot of nice add-ons. > + Less admin headaches. > > Cons; > - Giving up a bit of control. > - Possibly less flexible in ACL setups (but I don't have the energy > to do it right anyway) > > The threat of Github disappearing overnight should also be considered > a non-issue, since everyone has local copies of the whole repository > and a new central server can be put online without data losses. > > > Anything that I have not thought of? > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Alin Dreghiciu Software Developer - Looking for new projects! My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.blogspot.com http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development.
_______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
