+1 This discussion has also a legal component!
If someone does work and pushes this stuff to the repo on codehaus, then it's crystal clear that this is a contribution to codehaus. If one just maintains a 'private' fork on github, he could later also cange the license of his own stuff... LieGrue, strub --- On Mon, 8/29/11, Christopher Hunt <hu...@internode.on.net> wrote: > From: Christopher Hunt <hu...@internode.on.net> > Subject: Re: [mojo-dev] [DISCUSS] move back github stuff to codehaus > To: dev@mojo.codehaus.org > Date: Monday, August 29, 2011, 9:11 PM > On 30/08/2011, at 6:51 AM, Julien > Ponge wrote: > > > > > Take advantage of Git and GitHub for the ease of > collaboration, but retain a reference Git repository at > Codehaus where only commiters can make pushes (possible from > a GitHub fork where they already filtered incoming > contributions). That sounds like a win-win approach. > > > I believe that the problem is using Github's git repo as > the main scm for a Mojo project as opposed to using The > Codehaus git repo. > > Kind regards, > Christopher > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
