We can ask to Ben (and sonatype/central) but I'm almost sure he'll have nothing to let us use org.codehaus.* for existing projects. The question may be for future new plugins. Maybe we should reserve a new groupId and update maven to look at this groupId in addition of org.apache.maven.plugins and org.codehaus.mojo
About sources, I think it was already discussed to move everything to git thus it's just a time constraint to do it now For the target hosting github will be fine. I think we already reserved an organization (or two :-) https://github.com/maven-mojo/ https://github.com/codehaus-mojo/ We'll just have to clone repos there when they'll be available in RO on https://github.com/codehaus/ I'm not sure if Ben needs some helps for that About the issue tracker we may ask if we could have a Cloud hosting but it is limited to 1000 accounts and I'm not sure how many accounts in Codehaus Jira instance are related to mojo projects Otherwise we can move it to GitHub issues but we'll loose some content (it may be the opportunity to do some cleanup) About CI and automations ... Cloudbees, TravisCI .... We may ask/test About web sites .... GitHub sites ? About Confluence ... Trash ? GitHub Wikis ? About mailing lists ... Google Groups ?? Do I forget something ? On Fri, Feb 27, 2015 at 11:05 AM, Baptiste Mathus <bmat...@batmat.net> wrote: > Good point Anders, that's indeed something we want to double-check with > Codehaus people (btw, who else than Ben, is there anyone else?) > > 2015-02-27 10:50 GMT+01:00 Anders Hammar <and...@hammar.net>: > >> Hmmm. Is it only me that sees a problem with the org.codehaus.mojo >> groupId? Can we continue to use that in the future when syncing to central? >> >> Other than that I guess this is a good time to migrate to git instead of >> svn. >> >> /Anders >> >> On Fri, Feb 27, 2015 at 10:38 AM, David Karlsen <davidkarl...@gmail.com> >> wrote: >> >>> Codehaus.org does not respond - already EOL? ;) >>> The choises seem sane - except for sticking with svn. >>> git svn and pointing to the correct places for tags and branches should >>> make it possible to convert each module into a git repo (and use github for >>> hosting). >>> >>> 2015-02-27 10:24 GMT+01:00 Baptiste Mathus <bmat...@batmat.net>: >>> >>>> Hi all, >>>> >>>> Might be old news to you, but I guess some may not be aware of that >>>> news yet: >>>> Codehaus is coming to EOL... >>>> https://codehaus.org/ >>>> >>>> And it doesn't seem like it's considered to be taken over by other >>>> staff members if I read correctly the article (IIUC, this means you cannot >>>> even apply to help). >>>> >>>> So the question is, where do you thin the MOJO project go? And how to >>>> do we handle the migration? >>>> >>>> To sum up quickly, we use: >>>> * SCM : SVN (which would make github a hard choice for migration) >>>> * JIRA? Ask atlassian for a JIRA SaaS? >>>> https://www.atlassian.com/opensource/overview >>>> * CI? Ask CloudBees? >>>> https://www.cloudbees.com/resources/foss/program-details >>>> >>>> WDYT? >>>> >>>> -- >>>> Baptiste >>>> >>> >>> >>> >>> -- >>> -- >>> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >>> >> >> > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
