2015-02-27 11:37 GMT+01:00 Arnaud Héritier <aherit...@codehaus.org>:
> 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 > Already discussed [1], I was at least once the one sending the associated mail, but the conclusion, though I didn't send a summary VOTE mail since the answers clearly did show that the majority of people were 0 or -1. That's why I put SCM: SVN in the first place. Because though I'm personnaly inclined to use Git everywhere, I considered the MOJO developers as a whole was still more currently tied to svn. Though the new context might make people reconsider their opinion, granted. 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 > Apart from some very rare cases, we almost don't have Git repos currently. Is Ben planning to to expose some converted repo? Not sure that would work correctly with regards to tags, branches, etc. The mojo svn repo is quite big and I guess we'd need to do many specific things to migrate it over to a whole lot of smaller Git repositories. > > 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) > Yeah. I'm not sure GH issues would be sufficient. I guess we don't want to lose the MOJO project to be seen as a whole. For example, for Jenkins (as I know you know Arnaud), JIRA is used because it also offers many features unavailable in GH issues (though we may want to precisely list things we need to check if GH issue could indeed be enough). > About CI and automations ... Cloudbees, TravisCI .... We may ask/test > > About web sites .... GitHub sites ? > If GH, then yes, I suppose so. Maybe with a DNS record and the GH trick so that we can have maven-mojo.org or maven-mojo.io or something as the publicly-known URL. > About Confluence ... Trash ? GitHub Wikis ? > Do we even have pages on Confluence for the MOJO project? I thought everything was on mojo.codehaus.org. > > About mailing lists ... Google Groups ?? > Might be, yes. > > Do I forget something ? > [1] http://markmail.org/message/ywqoyhzt3wbbf2zn#query:+page:1+mid:k7ak5ii7aheliktv+state:results
