OK, just re-read the whole thread of mid-2011 about the same subject here [1].
[1] http://mojo.10943.n7.nabble.com/gwt-preparing-2-3-0-release-gt-github-td2126.html#a31920106 Basically, the same conclusion as now. I've crawled the archive a bit, and didn't find any vote as mentioned in the thread. Can someone confirm those votes never actually happen? If so, then I suppose we could call some votes about it. Thanks 2013/6/29 Baptiste MATHUS <bmat...@batmat.net> > OK. > Trying to sum up what was said, please comment/complete: > > * Basically, the majority seems to be OK with the /idea of a migration/. > ** But this would be really better done in a all-or-nothing way, so that > there's not many scm technos used at mojo@codehaus. > > * Hosting > ** Git is definitely already supported at Codehaus > ** IIUC Stephen, we would still need to get some more rights or something > (I suppose this is because we, by nature, create a lot of repos, so this is > unlikely something that could be left as-it without much hassle). > ** There's a debate of where the canonical repo should stay: somewhere at > Codehaus, or at GitHub? (anyway, one would then be the mirror of the other) > > * Contribution: lowering the barrier or not? > ** Some think that would help people propose patch/contribute, and also > help committers here to integrate patches btw. > ** Some are worried that would mainly cause the death to many projects > (here, that would affect some mojos?). Btw, I'd be interested in having > examples of that kind of death. > > * Technical aspects: > ** Migration could reasonably be automated. One git repo per mojo for > example. That's something many of us have already done, so I suppose that's > not the main issue. > > WDYT? Have I forgotten something? > > If we want to call for a vote about this, I guess we still need discussion > so that it doesn't get many -1 immediately and everybody loses his time and > we don't move forward :). > > Cheers > > > 2013/6/29 Fred Cooke <fred.co...@gmail.com> > >> Well Robert, it might not affect some, but it definitely affects others. >> Take me for example. I don't have and won't install SVN on my main dev >> machine. This mac is glacial at best, especially in a hot climate (30C >> where I live at the moment), so I don't dev on it much. If the mojos of >> interest to me had been in Git I'd have put some commits in before I >> discovered the release procedure stuff and decided not to. It's still on my >> TODO to convert the repos I need and make the changes I need, because it's >> a slight hassle and I'm far more than slightly busy. If it was already in >> Git it'd be clone, commit, push to github, done. So yeah, you'd have had >> some work out of me for sure. >> >> >> On Fri, Jun 28, 2013 at 10:12 PM, Robert Scholte < >> codeh...@sourcegrounds.com> wrote: >> >>> Yes ,I have these same concerns as Mark. >>> >>> Of all the Maven related projects which have been moved from SVN to GIT >>> I haven't seen more patches then before. So I'm not sure if this will >>> increase the number of contributions. >>> Don't get me wrong: I do understand the advantages of GIT, but >>> especially the cloning part makes it a lot easier to maintain your own >>> version (you don't depend on one of the plugin maintainers to approve >>> patches, if any is still alive). >>> >>> Robert >>> >>> >>> On Fri, 28 Jun 2013 16:55:52 +0200, Mark Struberg <strub...@yahoo.de> >>> wrote: >>> >>> >>>> >>>> There were some projects which moved to GIT. >>>> >>>> But after a short while they are now all DEAD! >>>> >>>> This has nothing to do with GIT itself (which I love), but with the >>>> missing 'ownership'. >>>> It's totally easy on github to just fork a project and fix your bug >>>> there - fully agree! >>>> But what about merging this stuff back? Well, this just does not happen >>>> most of the time. >>>> >>>> And this is the reason why I still love to have those projects over >>>> here at codehaus, eclipse or apache. >>>> >>>> Mostly because all people then know where to get the origin from. >>>> >>>> Again, this has nothing to do with GIT vs SVN. It just has to do with >>>> having some 'cannonical' source or not. >>>> >>>> LieGrue, >>>> strub >>>> >>>> >>>> >>>> >>>> ______________________________**__ >>>>> From: Jochen Wiedmann <jochen.wiedm...@gmail.com> >>>>> To: dev@mojo.codehaus.org >>>>> Sent: Friday, 28 June 2013, 16:07 >>>>> Subject: Re: [mojo-dev] Re: Mojo GIT migration or mirroring? >>>>> >>>>> >>>>> >>>>> Just asking: Does Github offer to provide an SVN mirror? Or is there >>>>> any other way to have a mirror without too much hazzle? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, Jun 28, 2013 at 9:50 AM, Fred Cooke <fred.co...@gmail.com> >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> >>>>>> For GIT users there are several ways to work with SVN, so that's >>>>>>> probably why this isn't that urgent. >>>>>>> >>>>>>> >>>>>> That's not really a good reason not to, because: >>>>>> >>>>>> * The SVN >> Git process isn't fast (because SVN is itself SLOW) >>>>>> * Each converter has to find motivation to bother setting this up >>>>>> and doing it in the first place. (read, they'll just not bother most of >>>>>> the >>>>>> time) >>>>>> >>>>>> * Each conversion will have a different set of hashes even if the >>>>>> other parameters are the same and thus won't be able to be collaborated >>>>>> between effectively. Having a single official mirror means others can >>>>>> effectively work together on "it" with the final result pulled back into >>>>>> SVN when ready and then automatically pushed back to Git again. The work >>>>>> flow is a pain, but still a lot better than suffering SVN in the first >>>>>> place. >>>>>> >>>>>> migrate > 1 official mirror (per mojo) > N unofficial mirrors/leave >>>>>> it alone >>>>>> >>>>>> I'm not ignoring the work involved in mirroring, just pointing out >>>>>> some facts. I don't think the Maven tool-set / infrastructure is 100% >>>>>> ready >>>>>> for Git, to be perfectly honest. The sink or swim method may be a good >>>>>> way >>>>>> to get it there, but might be painful, too. I'd certainly appreciate more >>>>>> Git friendly behaviour, though :-) >>>>>> >>>>>> Fred. >>>>>> >>>>>> Robert >>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, 27 Jun 2013 21:44:33 +0200, Lennart Jörelid < >>>>>>> lennart.jore...@gmail.com> wrote: >>>>>>> >>>>>>> >>>>>>> Folks... if anyone has an answer to this question, I would be all >>>>>>> ears. >>>>>>> >>>>>>>> Can I work with GIT or Mercurial here? Onto some mirror? >>>>>>>> If not - is there a process to distribute projects/plugins to >>>>>>>> GitHub? >>>>>>>> >>>>>>>> >>>>>>>> 2013/6/25 Lennart Jörelid <lennart.jore...@gmail.com> >>>>>>>> >>>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>>> >>>>>>>>> I wonder if the Mojo project has a structured way of migrating to a >>>>>>>>> distributed VCS (GIT, presumably, or Mercurial) for various >>>>>>>>> currently >>>>>>>>> SVN-based projects - or any policy on a 2-way mirroring between >>>>>>>>> the two >>>>>>>>> VCS'es. >>>>>>>>> >>>>>>>>> I believe distributed VCSs increase visibility and reduce >>>>>>>>> complexity for >>>>>>>>> donning a patch compared to the standard subversion way, >>>>>>>>> particularly with >>>>>>>>> the help of processes and services such as GitHub or BitBucket. >>>>>>>>> Anything >>>>>>>>> that can increase visibility and reduce hinders in contributing >>>>>>>>> patches to >>>>>>>>> projects is in itself a Good Thing. >>>>>>>>> >>>>>>>>> So ... is there a Git/Mercurial mirror or migration process for SVN >>>>>>>>> projects at Codehaus? >>>>>>>>> If so - where can I find access details? >>>>>>>>> If not - why? >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> +=============================**=+ >>>>>>>>> | 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 >>>>>>>>> +=============================**=+ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Using Opera's revolutionary email client: >>>> http://www.opera.com/mail/ >>>> >>>>> >>>>>>> ------------------------------**------------------------------** >>>>>>> --------- >>>>>>> To unsubscribe from this list, please visit: >>>>>>> >>>>>>> >>>>>>> http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> "That's what prayers are ... it's frightened people trying to make >>>>> friends with the bully!" >>>>> >>>>> Terry Pratchett. The Last Hero >>>>> >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> To unsubscribe from this list, please visit: >>>> >>>> >>>> http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> >>>> >>>> >>>> >>> >>> -- >>> Using Opera's revolutionary email client: http://www.opera.com/mail/ >>> >>> ------------------------------**------------------------------** >>> --------- >>> To unsubscribe from this list, please visit: >>> >>> >>> http://xircles.codehaus.org/**manage_email<http://xircles.codehaus.org/manage_email> >>> >>> >>> >> > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
