jenkins does it (1 plugin = 1 repo ) and I sincerely see no solution to avoid that. Each plugin or each lib has its own lifecycle and requires to have its own git repo to be clean That's why on jenkins we have the IRC bot to manage them But it is easier on github because they provide many APIs to do such remote management. On ASF side I don't think we'll have soon such tooling :( On the other hand the only annoying thing to do its the conversion itself and then to update projects (SCM ...). After that we could ask to sync them on github and we can easily provide some script to clone all repos from a given organisation. Unlike Jenkins we don't have a flow of repos creation really important on ASF side.
My 2 cents. Arnaud On Tue, Sep 4, 2012 at 10:23 PM, Olivier Lamy <ol...@apache.org> wrote: > 2012/9/4 Andrew Waterman <awate...@ecosur.mx>: >> The drools guys did a really nice move from Subversion a few years back. >> >> http://blog.athico.com/2010/12/drools-migrated-to-git.html >> >> One of the key things they did, was reorganize their poms and project >> structure. >> >> I'd be willing to help out. I think there could be a lot more to this move >> than just importing from subversion, but it depends on what you guys want to >> do. > > Yup I agree. > I use git on other oss projects (Apache: cloudstack and non Apache: > jenkins ...) and git svn for some asf projects. > Due to lack of support of sparse checkout in git, I (perso) don't want > we have to create a git repo per plugin etc... > IMHO That will be a pain to manage. > >> >> best wishes, >> >> Andrew >> >> On Sep 4, 2012, at 3:09 PM, "Jason Pyeron" <jpye...@pdinc.us> wrote: >> >>>> -----Original Message----- >>>> From: Jason van Zyl >>>> Sent: Tuesday, September 04, 2012 15:55 >>>> >>>> How's Git doing at Apache these days? >>>> >>>> Anyone interested in pursuing putting Maven in Git as the >>>> canonical SCM? >>> >>> Comments from the peanut gallery: It would make it very nice to contribute >>> back. >>> Since I do not have a sandbox access I have thrown away fixes because there >>> was >>> no efficient way to track them until they were accepted as patches. (same >>> problem in struts, commons, ...) >>> >>> We would be very happy here at PD Inc if that was done. >>> >>> -Jason Pyeron >>> >>> -- >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> - - >>> - Jason Pyeron PD Inc. http://www.pdinc.us - >>> - Principal Consultant 10 West 24th Street #100 - >>> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - >>> - - >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >>> This message is copyright PD Inc, subject to license 20080407P00. >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > -- ----- Arnaud Héritier 06-89-76-64-24 http://aheritier.net Mail/GTalk: aherit...@gmail.com Twitter/Skype : aheritier --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
