Hi, I should say, if Codehaus is no more, GitHub would be my obvious first choice of an alternative platform.
1. Version control. SVN is a dinosaur and a major impediment for contributing and integrating patches. Git provides a much more streamlined workflow from both committer's and contributor's point of view. I used GitHub for importing legacy SVN repos and it worked flawlessly. We never looked back to SVN. In short, let us ditch SVN completely and use this opportunity to migrate to git. 2. Maven web sites. It is possible to deploy them to GitHub pages for each project. Works a treat, and there is a GitHub maven site plugin to automate the process. 3. Issue tracking. Use GitHub issue tracking system. It is integrated with pull requests and commits, it is fast and lightweight, it has got milestones and it should cover all needs of a typical project. I for one will not miss Jira/FishEye/Cricible bundle, because Atlassian products have become a complete sh*t show in the last few years. For the same reason, I have major reservations against BitBucket. The only outstanding question is whether there is a way to somehow import the existing Jira content into GitHub. If that is not possible or straightforward, then there is a need to find Jira hosting solution elsewhere, at least for the historic content. 4. Code reviews See above: GitHub has a great support for reviewing the incoming pull requests. 5. Collaboration GitHub wikis cover that. Again, the question remains whether it is possible to import the existing content there. However, this may be a much lesser problem, because I reckon most of the content is deployed as part of maven sites, and the rest can be imported manually. At the same time, old irrelevant content could be dropped. 6. Continuous Integration This is one of the services that is not part of GitHub platform. Travis CI might pretty well cover that, and there are other solutions that are free for OSS projects. 7. Binary artifacts Most of the artifacts go into maven central, anything that does not fit there, could be hosted at Bintray. Not sure what else Codehaus provides that is not covered by the above. Kind regards, -- Sergei > >Friday, 27 February 2015 11:51 +0000 from Lennart Jörelid ><lennart.jore...@gmail.com>: >I second the opinions for moving to GitHub (or Bitbucket) instead of remaining >in SVN. >If doing so, I suggest we reuse as much as possible of the GitHub >infrastructure - Wiki, Issue Tracker, Mailing lists etc. >If we are already bound for some major migrations, let's make the best of them >- and a Distributed version control system is a productivity boost. >Also - is there really a point to maintain a particular GroupID (i.e. >org.codehaus). >I belive we could/should move Mojo's development efforts into the Apache >umbrella (why have 2 sources of normative plugins - apache and codehaus) to >simplify for users. >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 >>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 ! >-- >-- >+==============================+ >| Bästa hälsningar, >| [sw. "Best regards"] >| >| Lennart Jörelid >| EAI Architect & Integrator >| >| jGuru Europe AB >| Mölnlycke - Kista >| >| Email: l...@jguru.se >| URL: www.jguru.se >| Phone >| (skype): jgurueurope >| (intl): +46 708 507 603 >| (domestic): 0708 - 507 603 >+==============================+
