I follow Olivier. Myself I never said we should leave codehaus and certainly not move to GitHub. I'm in favor to migrate our SCM from a unique SVN to a set of git repositories @ Codehaus. If some developers want to clone the git repo from codehaus to github we won't avoid it (it is one advantage of DSCMs) but we'll take care that they'll be no release done out of codehaus.
Arnaud On Fri, Jun 24, 2011 at 3:03 PM, Olivier Lamy <[email protected]> wrote: > Hello, > POV (consider it "stallmanesque" if you want :-) ), perso I don't want > to see a non profitable organisation (Codehaus) depends on infra > provided by a private company (yes AFAIK github is a private company) > > FYI I have created some times ago codehaus-mojo organization > (https://github.com/codehaus-mojo). > We can "easily" setup mirroring mechanism to this place to use pull > request mechanism. > > > 2011/6/24 Mark Struberg <[email protected]>: > > I don't care about the name, I care about _who_ will do that? > > You would need to duplicate Xircles and a lot other things... > > > > LieGrue, > > strub > > > > --- On Fri, 6/24/11, Julien Ponge <[email protected]> wrote: > > > > From: Julien Ponge <[email protected]> > > Subject: Re: [mojo-dev] moving Mojo from svn to git > > To: [email protected] > > Date: Friday, June 24, 2011, 12:32 PM > > > > > > > > We'd better have a "codehaus-mojo" organization I think. > > Cheers > > > > -- > > Julien Ponge > > http://julien.ponge.info/ > > > > > > On vendredi 24 juin 2011 at 14:29, Mark Struberg wrote: > > > > +1 for each mojo plugin having it's own git module. > This makes a lot sense because of moving single projects out from codehaus, > etc. > > Also please note that tags and branches in GIT is over the _whole_ > repository, and _not_ over a subdirectory! > > > > I'd have no problem with adding more features to maven-scm-providers-git > or the maven-release-plugin/manager, but the tagging and branching would be > a killer. > > > > We could setup git-submodules to pin those together of course. > > > > @ndloof: codehaus has a git hosting ability and we would need to signup > codehaus as an organisation at github. But who would maintain that in this > case? > > > > LieGrue, > > strub > > > > --- On Fri, 6/24/11, Paul Gier <[email protected]> wrote: > > > > From: Paul Gier <[email protected]> > > Subject: Re: [mojo-dev] moving Mojo from svn to git > > To: [email protected] > > Date: Friday, June 24, 2011, 1:14 AM > > Not sure I understand you. I > > wasn't saying we should have a single git > > repo, I was suggesting that each plugin/project is located > > in it's own > > git repo under the common directory "mojo". Instead > > of prefixing the > > name of the repo with "mojo-". Either way there is > > one git repo per > > mojo project. This would be somewhat similar to how > > the repos would be > > set up on github. For example: > > > > https://github.com/codehaus-mojo/gwt-maven-plugin > > https://github.com/codehaus-mojo/buildnumber-maven-plugin > > > > On the codehaus repo we could have something like > > http://git.codehaus.org/mojo/gwt-maven-plugin.git > > > > On 06/23/2011 05:54 PM, Stephen Connolly wrote: > > until you try to release. > > > > if you release separately, you need separate git > > repositories. > > > > if you release at the same time, same git repo. > > > > so animal-sniffer would be one repo for the tools, one > > repo for each of > > the signatures. > > > > - Stephen > > > > --- > > Sent from my Android phone, so random spelling > > mistakes, random nonsense > > words and other nonsense are a direct result of using > > swype to type on > > the screen > > > > On 23 Jun 2011 23:41, "Paul Gier" <[email protected] > > <mailto:[email protected]>> > > wrote: > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > 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 > > >
