On Thu, Jun 23, 2011 at 11:37 PM, Robert Scholte <rfscho...@codehaus.org>wrote:
> 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) > yes we standardize our repo basing it on the actual mojo names : mojo-gwt-maven-plugin.git is good I think about the distinction between mojo status (dormant, sandbox....) I think it is useless to have this information on the SCM level. Thus a flat organization could be enough as we won't be able to reorganize git repositories ourself on codehaus side I think. The important is to keep the info in the documentation, the website and in sources. > 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? > Yes. The only thing I would like we try to control is that all releases of mojos published in central are coming from a tag in a git repo from codehaus. In theory nobody can publish under our groupId without using our Nexus @ Codehaus. But it is important to be able to easily find where sources are coming from. WDYT ? > > -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 > > > > >