Looking at http://git.codehaus.org/gitweb.cgi it looks to me we want something like jbehave has done. In our case that would mean something like "mojo-gwt-maven-plugin.git" or "mojo-gwtmavenplugin" or... our /trunk/mojo has 89 projects, I'm not sure if we have to do some cleanup here (could be part a the vote) I still believe we should keep the master at codehaus: one account to access all (scm as in svn or git, Jira, Bamboo, Confluence, Fisheye) According to this thread it's possible to sync this with github. So it seems like every could be pleased, right? -Robert
> From: hu...@internode.on.net > Date: Fri, 24 Jun 2011 07:13:43 +1000 > To: dev@mojo.codehaus.org > Subject: Re: [mojo-dev] moving Mojo from svn to git (was: preparing 2.3.0 > release -> github ) > > +1 for moving to git - much easier to work with remotely. > +1 for moving each mojo to its own git repo > > On the latter point, you *need* to do this. Anything that potentially > requires its own tag or branch needs its own git repo. > > Kind regards, > Christopher > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > >
