FYI, I have just created the organization maven-mojo https://github.com/maven-mojo . (https://github.com/mojo was already used).
2011/5/30 nicolas de loof <nicolas.del...@gmail.com>: > The idea is to move the code repo to github and deprecate the svn one (last > commit will be a README.txt file > GitHub is more than just Git hosting as you noticed. Pull Request, online > code editing and notes, and more nice web-based tools are great improvements > to make contributing easier. Hosting Git at codehaus would "just" make > merges easier compared to svn patches but not change the contribution > workflow. > I'd be pleased to see this happen at Mojo level, maybe the way Jenkins > plugins are grouped under jenkinsci organisation. It's anyway easy to > migrate a git repo from one github account to another. > > Le 30 mai 2011 13:47, Arnaud Héritier <aherit...@codehaus.org> a écrit : >> >> I like Git too but we should take care of few things : >> * We have to take care of giving the ability to all mojo projects. Perhaps >> under a dedicated mojo organization @ GitHub ? Or by working with Ben to >> have a Git support that satisfies our needs >> * The success of Github is mainly due to the fact that they added a lot of >> web features and documentations to ease to usage of git thus it is important >> in the choice as "just" moving to Git will increase the level to contribute >> to all of thus who don't use it again... (and GitHub provides a svn access >> to Git repositories for those who don't have the time to learn Git). >> Thus +0 to move to Git, +1 to move to GitHub but in all cases please try >> to do that at mojo level and not only for one plugin. >> Arnaud >> >> On Mon, May 30, 2011 at 12:17 PM, Olivier Lamy <ol...@apache.org> wrote: >>> >>> Hello, >>> What I understand here : Nicolas like to move "canonical" >>> gwt-maven-plugin scm repo to git (means sources not anymore in svn >>> @codehaus : or I misunderstand :-) ) >>> So two solutions : >>> * move to github >>> * ask ben or bob to have a git repo @codehaus (AFAIK it's supported ) >>> >>> Perso, I like git so why not :-) >>> >>> /Olivier >>> >>> Le 30 mai 2011 11:59, Arnaud Héritier <aherit...@codehaus.org> a écrit : >>> > How will you manage the synchro between SVN@Codehaus and GitHub ?? >>> > >>> > On Mon, May 30, 2011 at 11:10 AM, nicolas de loof >>> > <nicolas.del...@gmail.com> >>> > wrote: >>> >> >>> >> Hi folks, >>> >> I'll start preparation for a 2.3.0 release soon, >>> >> starting with this release, I'd like to move the canonical repo to >>> >> gitHub >>> >> to encourage more contributions, either via pull-request or direct >>> >> commit. >>> >> I'd like to follow the jenkins-way, with more releases (lets say, one >>> >> per >>> >> month) and lower contribution barrier. >>> >> I've cloned codehaus svn to >>> >> https://github.com/gwt-maven-plugin/gwt-maven-plugin, anyone from this >>> >> list >>> >> with spare time and motivation is welcome :P >>> >> Cheers, >>> >> Nicolas >>> > >>> > >>> >>> >>> >>> -- >>> Olivier Lamy >>> http://twitter.com/olamy | http://www.linkedin.com/in/olamy >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >> > > -- Olivier Lamy http://twitter.com/olamy | http://www.linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
