Re: [VOTE] Move Maven projects sources to git
+1 Vincent 2012/9/5 Olivier Lamy ol...@apache.org: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
Whilst it may work it's also rather horrible, unless every module in said repository shares the same version number and gets released at the same time. If however it's planned to go this route of a single repository, but separate release cadences for modules, some rework and new releases of the maven-release-plugin should probably first be ironed out. On 12/09/2012, at 12:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard.
Re: [VOTE] Move Maven projects sources to git
Is this not where the use of Review Board ( or preferably, Gerrit IMHO ) comes into play, any patch/commit goes thru the code review system prior to being accepted, and part of that review process is a required signoff that committer X has a contribution license for the project. On 12/09/2012, at 12:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: How is accepting a patch in Jira from user fuzzyBear without any further credentials attached (and no visible identification of a real or imagined person) different form a github pull request ? So while I agree about being careful about IP, i can't see our current regime being a bit different from github. You may argue that we'd want to tighten this, but this is the current reality for over 1 million committs. I have no idea of how many John Smith accounts there are in our jira, but we pretend to ignore the fact.
Re: [VOTE] Move Maven projects sources to git
2012/9/13 Mark Derricutt m...@talios.com: Whilst it may work it's also rather horrible, unless every module in said repository shares the same version number and gets released at the same time. If however it's planned to go this route of a single repository, but separate release cadences for modules, some rework and new releases of the maven-release-plugin should probably first be ironed out. That must work since 2.2 (see http://jira.codehaus.org/browse/MRELEASE-457 ) On 12/09/2012, at 12:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard. -- 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
Re: [VOTE] Move Maven projects sources to git
Yes, that works fine already. I've already used it for releasing Apache DeltaSpike where we do not have the pom directly under the root folder but in a ./deltaspike/ folder (in parallel to docs, etc) LieGrue, strub From: Olivier Lamy ol...@apache.org To: Maven Developers List dev@maven.apache.org Sent: Thursday, September 13, 2012 9:45 PM Subject: Re: [VOTE] Move Maven projects sources to git 2012/9/13 Mark Derricutt m...@talios.com: Whilst it may work it's also rather horrible, unless every module in said repository shares the same version number and gets released at the same time. If however it's planned to go this route of a single repository, but separate release cadences for modules, some rework and new releases of the maven-release-plugin should probably first be ironed out. That must work since 2.2 (see http://jira.codehaus.org/browse/MRELEASE-457 ) On 12/09/2012, at 12:13 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard. -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[RESULT] [VOTE] Move Maven projects sources to git
Hi, So it looks it was an interesting vote and topic with some nice/various views. (seems people looks more interested than voting on release :P ) The vote details are: +1 (binding PMC) krosenvold sconnolly aheritier benson milos barrie john casey emmanuel venisse herve boutemy olamy mark struberg pgier wayne fay robert scholte Brian fox +0.5 (binding) Dan Kulp Brett porter +0 (binding) stephane nicoll dennis lundberg mark struberg +1 (non pmc but committer) tony chemit anders igor +1 (non binding) Raffaele Jesse garvin manfred jason peyron baptiste mathus -1 (non binding) Chris So I see 15 +1 PMC binding votes (and some more community +1 votes too !) And 4 volunteers to help on various infra tasks! As we are 26 PMC [1], the majority is here so we can declare: vote passed. Regarding tasks for the migration, I will start an other email with details (etc..) Thanks -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy [1] http://people.apache.org/committers-by-project.html#maven-pmc - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+0 with a long explanation I'm really a friend of GIT in general. As some might remember I am even the guy who kicked off the GIT madness in maven land back in 2007 in the first place [1]. But I'm also a friend of using the right tool for the right job. GIT is great for projects which are not using dynamic modularity, because the concept of 'modules' is almost non-existing in GIT. I think GIT will work fine for maven-core and maven-scm, wagon or surefire which always get released as a whole. I think in those areas it would give us a certain benefit. But GIT sucks a bit when it comes to projects like maven-shared and maven-plugins which get released in portions. We already explained that with long words and we might have found a compromise which doesn't hurt too badly. But still it has to be verified if that works out. When it comes to community building I have my concerns that GIT will be of much benefit. We use GIT very successfully over in Apache DeltaSpike where it is very clear where the cannonical repository lives. If this is clear and all people know where they should get the main stuff from, then GIT is really great. And please forget about pull requests from some unknown github repos. We now count the year 1 after goog-vs-orcl and must really be cautious about intellectual property! This is just not possible because of the legal impacts as github doesnt check an authority of the authors. But here is another example where it did not work out: A few days ago a guy pinged us on #maven about the osxappbundle-maven-plugin. He just found 20++ versions around on github and none of them was working correctly. He didn't even know that the original one was still maintained in SVN in codehaus. So we went through all the versions on github and most of them contained different patches. And actually all of them only worked for a very specific situation. There was exactly 0 of them which worked on all 3 last OSX versions! What does this mean? If it's so much easier to make a private clone on github and fix exactly my own problem which I have right now, then this doesn't include feedback from others. And this not only bypasses the community but also confuses others. I'd really appreciate if people would be more careful with their clones and github would introduce a mandatory field [x] my original work [x] original code can be found: but that's another story. My summary: a project of that size is only working if there is a community around it. And whether you like a cannonical repo or not, it to some degrees forces users to talk with each others and give feedback! LieGrue, strub [1] https://github.com/struberg/maven-scm-providers-git/commit/e670863b2b03e158c59f34af1fee20f91b2bd852 - Original Message - From: Olivier Lamy ol...@apache.org To: Maven Developers List dev@maven.apache.org Cc: Sent: Wednesday, September 5, 2012 1:04 PM Subject: [VOTE] Move Maven projects sources to git Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 Emmanuel On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
But GIT sucks a bit when it comes to projects like maven-shared and maven-plugins which get released in portions. We already explained that with long words and we might have found a compromise which doesn't hurt too badly. But still it has to be verified if that works out. Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard. We now count the year 1 after goog-vs-orcl and must really be cautious about intellectual property! How is accepting a patch in Jira from user fuzzyBear without any further credentials attached (and no visible identification of a real or imagined person) different form a github pull request ? So while I agree about being careful about IP, i can't see our current regime being a bit different from github. You may argue that we'd want to tighten this, but this is the current reality for over 1 million committs. I have no idea of how many John Smith accounts there are in our jira, but we pretend to ignore the fact. But here is another example where it did not work out: A few days ago a guy pinged us on #maven about the osxappbundle-maven-plugin. He just found 20++ versions around on github and none of them was working correctly. He didn't even know that the original one was still maintained in SVN in codehaus. So we went through all the versions on github and most of them contained different patches. And actually all of them only worked for a very specific situation. There was exactly 0 of them which worked on all 3 last OSX versions! What does this mean? It means you can't ignore your community and not maintain software when you're on git. But git has opened this entry point no matter what, it's like a box that's been opened for the whole community and there's no way back on that. The exclusive modification right that svn commit bit used to mean is gone. Once you learn to maintain a git fork you can permanently maintain a fork much simpler than before. It's actually something I think we should embrace, not frown upon. On my last project, we had *permanent* forks of three major frameworks that git allowed us to rebase and maintain with minimal or no effort. Characteristic of these patches were that A) we had submitted them but they were rejected B) we were invested in deprecated stuff that the communit weren't maintaing any more C) it was simply not of a quality that would be accepted Looking blindly at the github network graph does not give you this story, and it's like there's a whole new world of options available to OSS users. The act of submitting a patch (=pull request) simply means the creator of the patch is interested in submitting. The fact that I can browse all kinds of different hacks people have applied to my code does not really mean they are submitted or intended for submission. Combined with mailing list issue tracker activity, the stuff going on at github /is/ your community. If you see something cool in a branch on github, just add a comment requesting the author to submit this as a patch (or pull request if you permit it). If we can't accept pull requests we'll just have to do some other cool hack. Maybe we could write github plugin that could auto-submit a jira ;) It's all options, and we decide Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
well, for gods sake and (and for the peace of the bits on my ssd) I move my vote to +1 as well LieGrue, strub - Original Message - From: Kristian Rosenvold kristian.rosenv...@gmail.com To: Maven Developers List dev@maven.apache.org; Mark Struberg strub...@yahoo.de Cc: Sent: Tuesday, September 11, 2012 2:13 PM Subject: Re: [VOTE] Move Maven projects sources to git But GIT sucks a bit when it comes to projects like maven-shared and maven-plugins which get released in portions. We already explained that with long words and we might have found a compromise which doesn't hurt too badly. But still it has to be verified if that works out. Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard. We now count the year 1 after goog-vs-orcl and must really be cautious about intellectual property! How is accepting a patch in Jira from user fuzzyBear without any further credentials attached (and no visible identification of a real or imagined person) different form a github pull request ? So while I agree about being careful about IP, i can't see our current regime being a bit different from github. You may argue that we'd want to tighten this, but this is the current reality for over 1 million committs. I have no idea of how many John Smith accounts there are in our jira, but we pretend to ignore the fact. But here is another example where it did not work out: A few days ago a guy pinged us on #maven about the osxappbundle-maven-plugin. He just found 20++ versions around on github and none of them was working correctly. He didn't even know that the original one was still maintained in SVN in codehaus. So we went through all the versions on github and most of them contained different patches. And actually all of them only worked for a very specific situation. There was exactly 0 of them which worked on all 3 last OSX versions! What does this mean? It means you can't ignore your community and not maintain software when you're on git. But git has opened this entry point no matter what, it's like a box that's been opened for the whole community and there's no way back on that. The exclusive modification right that svn commit bit used to mean is gone. Once you learn to maintain a git fork you can permanently maintain a fork much simpler than before. It's actually something I think we should embrace, not frown upon. On my last project, we had *permanent* forks of three major frameworks that git allowed us to rebase and maintain with minimal or no effort. Characteristic of these patches were that A) we had submitted them but they were rejected B) we were invested in deprecated stuff that the communit weren't maintaing any more C) it was simply not of a quality that would be accepted Looking blindly at the github network graph does not give you this story, and it's like there's a whole new world of options available to OSS users. The act of submitting a patch (=pull request) simply means the creator of the patch is interested in submitting. The fact that I can browse all kinds of different hacks people have applied to my code does not really mean they are submitted or intended for submission. Combined with mailing list issue tracker activity, the stuff going on at github /is/ your community. If you see something cool in a branch on github, just add a comment requesting the author to submit this as a patch (or pull request if you permit it). If we can't accept pull requests we'll just have to do some other cool hack. Maybe we could write github plugin that could auto-submit a jira ;) It's all options, and we decide Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1, and I'm willing to volunteer if you still need more people. On 09/05/2012 06:04 AM, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
On 09/11/2012 07:13 AM, Kristian Rosenvold wrote: But GIT sucks a bit when it comes to projects like maven-shared and maven-plugins which get released in portions. We already explained that with long words and we might have found a compromise which doesn't hurt too badly. But still it has to be verified if that works out. Tagging the whole repo svn-style definitely works, and the maven-plugins repo isn't that big either. We could consider stephen's subdivision suggestion, but really I think it's totally viable to just leave one big repo. We're talking 37mb for the full history of everything, give or take a few bytes. Not too much by any modern standard. I would vote for just splitting the Maven plugins into separate git repos. I normally don't find myself needing to checkout/build/work on multiple plugins at once, so giving them each a separate lifecycle would be fine, IMO. But we could probably leave these migrations for later after we migrate Maven core and some of the other more monolithic projects. We now count the year 1 after goog-vs-orcl and must really be cautious about intellectual property! How is accepting a patch in Jira from user fuzzyBear without any further credentials attached (and no visible identification of a real or imagined person) different form a github pull request ? So while I agree about being careful about IP, i can't see our current regime being a bit different from github. You may argue that we'd want to tighten this, but this is the current reality for over 1 million committs. I have no idea of how many John Smith accounts there are in our jira, but we pretend to ignore the fact. I agree, if anything git patches give us a bit more protection regarding IP because it tracks the name and email of the author. In addition, we could make it our policy to not accept patches in git that don't appear to have a valid author name and email. But here is another example where it did not work out: A few days ago a guy pinged us on #maven about the osxappbundle-maven-plugin. He just found 20++ versions around on github and none of them was working correctly. He didn't even know that the original one was still maintained in SVN in codehaus. So we went through all the versions on github and most of them contained different patches. And actually all of them only worked for a very specific situation. There was exactly 0 of them which worked on all 3 last OSX versions! What does this mean? It means you can't ignore your community and not maintain software when you're on git. But git has opened this entry point no matter what, it's like a box that's been opened for the whole community and there's no way back on that. The exclusive modification right that svn commit bit used to mean is gone. Once you learn to maintain a git fork you can permanently maintain a fork much simpler than before. It's actually something I think we should embrace, not frown upon. On my last project, we had *permanent* forks of three major frameworks that git allowed us to rebase and maintain with minimal or no effort. Characteristic of these patches were that A) we had submitted them but they were rejected B) we were invested in deprecated stuff that the communit weren't maintaing any more C) it was simply not of a quality that would be accepted Looking blindly at the github network graph does not give you this story, and it's like there's a whole new world of options available to OSS users. The act of submitting a patch (=pull request) simply means the creator of the patch is interested in submitting. The fact that I can browse all kinds of different hacks people have applied to my code does not really mean they are submitted or intended for submission. Combined with mailing list issue tracker activity, the stuff going on at github /is/ your community. If you see something cool in a branch on github, just add a comment requesting the author to submit this as a patch (or pull request if you permit it). If we can't accept pull requests we'll just have to do some other cool hack. Maybe we could write github plugin that could auto-submit a jira ;) It's all options, and we decide Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
Changing my vote to +1 based on Kristian and Mark's recent exchanges. Wayne On Thu, Sep 6, 2012 at 11:28 AM, Wayne Fay wayne...@gmail.com wrote: [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) +0.5 Sorry but I will be no help, I have little git experience except as an end user. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I don't think it's IF we should move to git, but WHEN and now seems to be the right time. +1 Robert Op Tue, 11 Sep 2012 14:49:46 +0200 schreef Paul Gier pg...@redhat.com: +1, and I'm willing to volunteer if you still need more people. On 09/05/2012 06:04 AM, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I'm +1 On Tue, Sep 11, 2012 at 1:39 PM, Robert Scholte rfscho...@apache.orgwrote: I don't think it's IF we should move to git, but WHEN and now seems to be the right time. +1 Robert Op Tue, 11 Sep 2012 14:49:46 +0200 schreef Paul Gier pg...@redhat.com: +1, and I'm willing to volunteer if you still need more people. On 09/05/2012 06:04 AM, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --**--**- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**orgdev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I think it would be a very pragmatic move to simply leave the maven-plugins project unmigrated until we have established documentation and tool support to a level where we're happy with whatever solution we choose. I think the only really disasterous version we could end up with is the one which is currently in the maven-plugins asf repo, where the structure of the repo changes entirely as you checkout a tag. Other than that I don't /really/ think one-repo-per-plugin, one big repo or some other subdivision (maven-xAR-plugins comes to mind) is going to make that much of a difference. Kristian 2012/9/6 Brett Porter br...@apache.org: +0.5 if it makes devs or patchers lives easier No time to help, and I'd like to see a clearer understanding of how we'll convert non-t/b/t-layout repos before we end up with 50 repositories as others have said. BTW, if anyone is looking at doing that, I found the svn2git worked well for filtering, without having to resort to an svndumpfilter first (I believe it even addresses moves from outside of the subtree's history). - Brett On 05/09/2012, at 4:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 (non binding). Willing to help. Git shows clear advantages over svn. Le 5 sept. 2012 14:37, Garvin LeClaire garvin.lecla...@gmail.com a écrit : +1 (non-binding) -- Regards, Garvin LeClaire garvin.lecla...@gmail.com On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar and...@hammar.net wrote: +1 (non-binding) But I don't have the hard-core git knowledge to help out in the move. Would probably do more harm than good. :-) /Anders On Wed, Sep 5, 2012 at 2:19 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
OMG, had a similar experience only recently. We should incorporate a module which got created by another company. We requested to get the source and so we got access to their SVN repo. The first thing I saw was 35 directories with almost identical sources. And no, that was not managed as SVN branches (svn copy) but they did 'branches' by doing a recursive copy of their sources on the file system (cp -r into a new directory with incremental numbers) and then checked that in as fresh sources with svn add. What should I say... Anyway, that is heavily offtopic already and I assume that we don't have any devs of that kind around actively working on maven ;) LieGrue, strub - Original Message - From: Chris Graham chrisgw...@gmail.com To: Maven Developers List dev@maven.apache.org Cc: Sent: Thursday, September 6, 2012 2:33 AM Subject: Re: [VOTE] Move Maven projects sources to git I knew someone would misread that. I was not referring to anyone on this list. People on this list are at the pointy end of the stick, although we have a spread of abilities, most are in the upper end of the scale. The reason for this is simple. It's because to do it because we like it, a passion as it were. And that's when you see people at their best. Even with differences of opinion (and experience) such as this. Compare this with the corporate world in which I work. In the quest for the immortal dollar, the bar is being LOWERED, not raised. The average skill level of people is stunningly low. Believe it or not, I _STILL_ have arguments with people as to whether people need to check things in or not. And how to check in, and that you DO need to do an update first, before you commit, and not delete the dir in SVN and then add everything afresh (thus wiping out other people's changes). Sad but true. In this day and age. I was referring 'people of questionable parentage' from my previous project. Several vendors did not have any SCM at all. Fine, give them Hg. But don't force those with mature processes in place to change. Especially when no one has any skills or experience in Hg/git on how/why/etc to set up and manage multiple repos. Even those who were experienced in using GIT, they ended up with hundreds of repos, and it became a real mess to manage. Oh, and stop stupid things like checking built binaries into repos... As robert points out, it's not just the technical reasons for a change that need to be considered, there are all of the other reasons, training, knowledge, support etc that also need to be considered. As someone else points out, if CVS still works for you, fine, stick with it. So, I have a broader view of SCM usage. It's not just the tool being used, it *must* encompass HOW it is to be used. -Chris (who is clearly wearing his SCM hat today... :-) ) On Wed, Sep 5, 2012 at 11:24 PM, Benson Margulies bimargul...@gmail.comwrote: Chris, Just whom amongst us are you labeling 'a few immature devs'? Many of us here have been using both git and svn, extensively, for years now, and have a preference for git based on plenty of practical experience. While git is new-ish at the ASF, it's official, and a growing list of projects are using it Many of the, ahem, outboard components of Maven are in git already. Speaking for myself, I've used svn, I've used 'git svn', and I've used git. Plenty. And it's my considered judgement that git would be better for this project, and I voted as such. Please don't cast asparagus on my by indirectly calling me a cultist. --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
Hi, As Kristian said, there's already a Zillion articles referencing it. Personnally, (DVCS advantage) I really like being able to work locally/offline, going back and forth in the history and branches, *very quickly*. Having no difficulty to navigate between ideas without much burden. Being able to make many commits and totally reworking history to tell a good story before going public (I've heard Git is particularly advanced in this area even amongst DVCS). Cheers 2012/9/6 Chris Graham chrisgw...@gmail.com On Thu, Sep 6, 2012 at 4:48 PM, Baptiste MATHUS wrote: +1 (non binding). Willing to help. Git shows clear advantages over svn. Lots of people have made that statement. Along with the advantages of DSCM, as it's implicitly obvious. Well, I'm saying that its NOT obvious. Care to educate me? -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: [VOTE] Move Maven projects sources to git
[+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) +0.5 Sorry but I will be no help, I have little git experience except as an end user. Wayne - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+0 I personally don't have the git knowledge to be able to help, but I'm interested in learning the new technology. In my view the tooling for git is not yet as good as for SVN, but it's getting there. We have two important things to look out for: 1. Support for git at the ASF, and documentation about it, is not nearly as good as for SVN yet. That will hopefully change over time as more and more projects move, but it's still something we need to be prepared for. 2. As with all things new there will be mistakes made in the beginning. Let us start small, with one or two sub-projects, and learn from that experience before we try to do a full scale migration. I suggest starting with maven-3, and maybe scm or wagon which are pretty stand-alone projects. On 2012-09-05 13:04, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I can help out a bit with documentation as I've helped authoring a guideline over at the CouchDb and DeltaSpike projects (where we both use GIT) http://wiki.apache.org/couchdb/Git_At_Apache_Guide http://wiki.apache.org/couchdb/SVNvsGIT Some of it needs updating. Especially since I consider the 'experiment' to be successful. LieGrue, strub - Original Message - From: Dennis Lundberg denn...@apache.org To: Maven Developers List dev@maven.apache.org Cc: Sent: Thursday, September 6, 2012 8:53 PM Subject: Re: [VOTE] Move Maven projects sources to git +0 I personally don't have the git knowledge to be able to help, but I'm interested in learning the new technology. In my view the tooling for git is not yet as good as for SVN, but it's getting there. We have two important things to look out for: 1. Support for git at the ASF, and documentation about it, is not nearly as good as for SVN yet. That will hopefully change over time as more and more projects move, but it's still something we need to be prepared for. 2. As with all things new there will be mistakes made in the beginning. Let us start small, with one or two sub-projects, and learn from that experience before we try to do a full scale migration. I suggest starting with maven-3, and maybe scm or wagon which are pretty stand-alone projects. On 2012-09-05 13:04, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
On 09/05/2012 08:39 AM, Olivier Lamy wrote: I'm a bit curious to see if that will increase externals contributions. I think plain Git is only marginally more friendly for external contributors than Subversion. Yes you can create a local branch and update it against trunk changes, but you still need to manually attach patches to JIRA; reviewing and updating patches this way is painful. It is GitHub, principally pull requests but also the ability to comment on individual diff lines in any published revision, which is far and away better for collaboration. If Maven and satellite projects are moved to Git hosted on Apache servers only, I do not see contributions being much easier. The better approach to my mind would be to use GitHub-hosted repositories for all collaboration and ongoing development, and just mirror to Apache clones if necessary for legal reasons. Is that possible? If not, GitHub mirrors could still be used for pull requests, but the committer would have to do some manual synchronization. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
forget pulls from github. Everyone can create a commit which is allegedly from you (email and name) and others will have no whatever chance to verify that! Now combine that with complex scenarios where you pull in more than a simple change which you can track manually and you have the perfect way for someone to introduce backdoors. By having the authorisation plus authentication on an ASF server and always verifying it on a push (and keeping the push logs) we can at least verify a chain. LieGrue, strub - Original Message - From: Jesse Glick jgl...@cloudbees.com To: dev@maven.apache.org Cc: Sent: Thursday, September 6, 2012 9:35 PM Subject: Re: [VOTE] Move Maven projects sources to git On 09/05/2012 08:39 AM, Olivier Lamy wrote: I'm a bit curious to see if that will increase externals contributions. I think plain Git is only marginally more friendly for external contributors than Subversion. Yes you can create a local branch and update it against trunk changes, but you still need to manually attach patches to JIRA; reviewing and updating patches this way is painful. It is GitHub, principally pull requests but also the ability to comment on individual diff lines in any published revision, which is far and away better for collaboration. If Maven and satellite projects are moved to Git hosted on Apache servers only, I do not see contributions being much easier. The better approach to my mind would be to use GitHub-hosted repositories for all collaboration and ongoing development, and just mirror to Apache clones if necessary for legal reasons. Is that possible? If not, GitHub mirrors could still be used for pull requests, but the committer would have to do some manual synchronization. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
2012/9/6 Jesse Glick jgl...@cloudbees.com: On 09/05/2012 08:39 AM, Olivier Lamy wrote: I'm a bit curious to see if that will increase externals contributions. I think plain Git is only marginally more friendly for external contributors than Subversion. Yes you can create a local branch and update it against trunk changes, but you still need to manually attach patches to JIRA; reviewing and updating patches this way is painful. Maybe we can improve tooling I started long ago (http://olamy.blogspot.fr/2011/11/from-pull-request-to-jira-issue.html). As jira is definitely better for issue management ! It is GitHub, principally pull requests but also the ability to comment on individual diff lines in any published revision, which is far and away better for collaboration. If Maven and satellite projects are moved to Git hosted on Apache servers only, I do not see contributions being much easier. The better approach to my mind would be to use GitHub-hosted repositories for all collaboration and ongoing development, and just mirror to Apache clones if necessary for legal reasons. Is that possible? If not, GitHub mirrors could still be used for pull requests, but the committer would have to do some manual synchronization. For legal reasons, not possible. BTW contributors can use github to propose pull request to git mirrors @github github.com/apache so we can fetch changes from others (hey it's a dvcs :-) ) or use generated patches. - 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
Re: [VOTE] Move Maven projects sources to git
github pull requests can be accepted even though we are ASF hosted, in fact github will automatically close the corresponding pull request as the commit is pushed back through the git mirroring from asf-github.com/apache. I think github is extremely important, but they have also managed to be smart enough to make themselves unimportant. If I understand this correctly we maintain a written record of all pull requests by echoing their full content to some mailing list, so effectively we do not need patches attached to jira. Someone please do correct me if I'm wrong on this. Personally I think the git/github/asf combo is mindbendingly more flexible and open for submissions than svn ever will be; using git-svn and github can get you close but it's a dirty workflow sometimes and it's really mostly sustainable for people with strong git skills. Kristian 2012/9/6 Jesse Glick jgl...@cloudbees.com: On 09/05/2012 08:39 AM, Olivier Lamy wrote: I'm a bit curious to see if that will increase externals contributions. I think plain Git is only marginally more friendly for external contributors than Subversion. Yes you can create a local branch and update it against trunk changes, but you still need to manually attach patches to JIRA; reviewing and updating patches this way is painful. It is GitHub, principally pull requests but also the ability to comment on individual diff lines in any published revision, which is far and away better for collaboration. If Maven and satellite projects are moved to Git hosted on Apache servers only, I do not see contributions being much easier. The better approach to my mind would be to use GitHub-hosted repositories for all collaboration and ongoing development, and just mirror to Apache clones if necessary for legal reasons. Is that possible? If not, GitHub mirrors could still be used for pull requests, but the committer would have to do some manual synchronization. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
same here but I'm convinced git can help in some cases, like maintaining branches in parallel so I'm finally +1 Regards, Hervé Le jeudi 6 septembre 2012 20:53:39 Dennis Lundberg a écrit : +0 I personally don't have the git knowledge to be able to help, but I'm interested in learning the new technology. In my view the tooling for git is not yet as good as for SVN, but it's getting there. We have two important things to look out for: 1. Support for git at the ASF, and documentation about it, is not nearly as good as for SVN yet. That will hopefully change over time as more and more projects move, but it's still something we need to be prepared for. 2. As with all things new there will be mistakes made in the beginning. Let us start small, with one or two sub-projects, and learn from that experience before we try to do a full scale migration. I suggest starting with maven-3, and maybe scm or wagon which are pretty stand-alone projects. On 2012-09-05 13:04, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Move Maven projects sources to git
Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
+1 and volunteer for infra help. 2012/9/5 Olivier Lamy ol...@apache.org: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy -- 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
Re: [VOTE] Move Maven projects sources to git
+1 Will volunteer Den 5. sep. 2012 kl. 13:04 skrev Olivier Lamy ol...@apache.org: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
+1 and volunteer for infra help. I'll find the opportunity to launch few more shells commands per day :-) Arnaud On Wed, Sep 5, 2012 at 1:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
On Wed, 5 Sep 2012 13:04:29 +0200 Olivier Lamy ol...@apache.org wrote: +1, but can not be volunteer no time at all ATM. Next month should be better to help you guys and do some code at last... tony. Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
-1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
+1 Il giorno 05/set/2012 13:04, Olivier Lamy ol...@apache.org ha scritto: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
+1, git is far beyond being a 'fad' -- jesse mcconnell jesse.mcconn...@gmail.com On Wed, Sep 5, 2012 at 6:41 AM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 (non-binding) But I don't have the hard-core git knowledge to help out in the move. Would probably do more harm than good. :-) /Anders On Wed, Sep 5, 2012 at 2:19 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 (non-binding) -- Regards, Garvin LeClaire garvin.lecla...@gmail.com On Wed, Sep 5, 2012 at 8:33 AM, Anders Hammar and...@hammar.net wrote: +1 (non-binding) But I don't have the hard-core git knowledge to help out in the move. Would probably do more harm than good. :-) /Anders On Wed, Sep 5, 2012 at 2:19 PM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I think Chris ask more what will that change for our projects for community point. Perso I'm a bit curious to see if that will increase externals contributions. I don't want to do that only to ease life of private maven forkers. But so this discussion must in a separate thread not in the vote thread. 2012/9/5 Kristian Rosenvold kristian.rosenv...@gmail.com: The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - 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
Re: [VOTE] Move Maven projects sources to git
+1 binding can help On Wed, Sep 5, 2012 at 7:45 AM, Jesse McConnell jesse.mcconn...@gmail.com wrote: +1, git is far beyond being a 'fad' -- jesse mcconnell jesse.mcconn...@gmail.com On Wed, Sep 5, 2012 at 6:41 AM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1, cannot help unfortunatelely Milos On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
It's not a matter of thinking that git is like SVN at all. It's the exact opposite in fact; they are different, to the extent that it entails a whole new approach. We have a well resourced, well understood, well supported tool and mature practices with our current SVN. All I am saying is that we really should stop and think as to whether we want to throw that out. I, personally am not convinced. At the end of the day, it's more about WHAT we produce (maven, plugins etc) than the TOOLS (SVN, git, etc) we use. For those who want to use git, fine stick with git SVN, but don't force me to learn a new tool; I do enough of that already. (and I've just come from a project where the personal preferences of a few immature devs forced the abandonment of good mature practices and had Hg shoved down our throats; and this is a $40 Billion dollar company, let's not make the same mistake here). -Chris Sent from my iPhone On 05/09/2012, at 9:41 PM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
fwiw, i suspect most of us that have voted simply prefer working with git over svn certainly anyone that has had to manage branching and merging with svn vs git would understand...it is simply better with git. sorry you had management push you to use Hg, but git is a solid upgrade over svn at this pointlook at the eclipse foundation, svn was trying to replace cvs there for years and with cvs being turned off everyone is going to git, and its but a nice upgrade. svn was never natively supported out of the gate with eclipse without extra installation steps...git is native in eclipse with the egit project. cvs is being turned off soon there and afaik no project chose to migrate to svn from cvs, they simply switched to git :) cheers, jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Wed, Sep 5, 2012 at 8:05 AM, Chris Graham chrisgw...@gmail.com wrote: It's not a matter of thinking that git is like SVN at all. It's the exact opposite in fact; they are different, to the extent that it entails a whole new approach. We have a well resourced, well understood, well supported tool and mature practices with our current SVN. All I am saying is that we really should stop and think as to whether we want to throw that out. I, personally am not convinced. At the end of the day, it's more about WHAT we produce (maven, plugins etc) than the TOOLS (SVN, git, etc) we use. For those who want to use git, fine stick with git SVN, but don't force me to learn a new tool; I do enough of that already. (and I've just come from a project where the personal preferences of a few immature devs forced the abandonment of good mature practices and had Hg shoved down our throats; and this is a $40 Billion dollar company, let's not make the same mistake here). -Chris Sent from my iPhone On 05/09/2012, at 9:41 PM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+0 S. On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
Chris, Just whom amongst us are you labeling 'a few immature devs'? Many of us here have been using both git and svn, extensively, for years now, and have a preference for git based on plenty of practical experience. While git is new-ish at the ASF, it's official, and a growing list of projects are using it Many of the, ahem, outboard components of Maven are in git already. Speaking for myself, I've used svn, I've used 'git svn', and I've used git. Plenty. And it's my considered judgement that git would be better for this project, and I voted as such. Please don't cast asparagus on my by indirectly calling me a cultist. --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
2012/9/5 Chris Graham chrisgw...@gmail.com: It's not a matter of thinking that git is like SVN at all. It's the exact opposite in fact; they are different, to the extent that it entails a whole new approach. We have a well resourced, well understood, well supported tool and mature practices with our current SVN. All I am saying is that we really should stop and think as to whether we want to throw that out. I, personally am not convinced. At the end of the day, it's more about WHAT we produce (maven, plugins etc) than the TOOLS (SVN, git, etc) we use. For those who want to use git, fine stick with git SVN, but don't force me to learn a new tool; I do enough of that already. (and I've just come from a project where the personal preferences of a few immature devs forced the abandonment of good mature practices and had Hg shoved down our throats; and this is a $40 Billion dollar company, let's not make the same mistake here). Sorry for that. But (perso) I use git on some projects and I find it fine. Moving from svn to git is a bit simple (just some commands to replace). BTW We will have to document some basic stuff (replace the page http://maven.apache.org/developers/conventions/svn.html with common useful git commands) -Chris Sent from my iPhone On 05/09/2012, at 9:41 PM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 -- 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
Re: [VOTE] Move Maven projects sources to git
I'm +0.5 on everything that currently has the trunk/tags/branches setup in SVN. -1 on things that are not setup that way right now until more discussions and agreement can be made on how that should be approached. Really, I think we should just do Maven core and maybe one or two other simple ones for now and see how that goes. If that goes well over then next 3 months or so, expand a little more. Dan On Sep 5, 2012, at 7:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
We only move things we are satisfied with. But we don't vote on each item unless there turns out to be some real issues to solve. Most of the maven projects already have excellent git repositories at http://git.apache.org/, for these it's just a modified scm url and the flip of a switch or two. So there's basically only a few cases to be solved. Luckily we have good repos to use as starting point for some hard-core filter-branch/relocation stuff. I was planning to do this for codehaus a year ago, I suspect I can use the scripts I'd make for this at @haus too. Kristian 2012/9/5 Daniel Kulp dk...@apache.org: I'm +0.5 on everything that currently has the trunk/tags/branches setup in SVN. -1 on things that are not setup that way right now until more discussions and agreement can be made on how that should be approached. Really, I think we should just do Maven core and maybe one or two other simple ones for now and see how that goes. If that goes well over then next 3 months or so, expand a little more. Dan On Sep 5, 2012, at 7:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
2012/9/5 Kristian Rosenvold kristian.rosenv...@gmail.com: We only move things we are satisfied with. But we don't vote on each item unless there turns out to be some real issues to solve. Most of the maven projects already have excellent git repositories at http://git.apache.org/, Note: current ASF projects using git as canonical scm are located here: https://git-wip-us.apache.org/repos/asf for these it's just a modified scm url and the flip of a switch or two. So there's basically only a few cases to be solved. Luckily we have good repos to use as starting point for some hard-core filter-branch/relocation stuff. I was planning to do this for codehaus a year ago, I suspect I can use the scripts I'd make for this at @haus too. Kristian 2012/9/5 Daniel Kulp dk...@apache.org: I'm +0.5 on everything that currently has the trunk/tags/branches setup in SVN. -1 on things that are not setup that way right now until more discussions and agreement can be made on how that should be approached. Really, I think we should just do Maven core and maybe one or two other simple ones for now and see how that goes. If that goes well over then next 3 months or so, expand a little more. Dan On Sep 5, 2012, at 7:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - 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
Re: [VOTE] Move Maven projects sources to git
+1 -- Regards, Igor On 12-09-05 7:04 AM, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 non binding In terms of learning more about git, there are a LOT of free resources available including books and other documentation as well as things like live office hours at github and so on. GitHub is also open sourcing all their training material so there will be more as well.. and lots of it is around git concepts and not github specifics. A small word of warning though.. once you have learned git and enjoyed the benefits you will feel bad whenever you use another version control system. manfred On Wed, September 5, 2012 4:41 am, Arnaud Héritier wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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
Re: [VOTE] Move Maven projects sources to git
No-one is using cvs anymore. That's a wrong assumption, sad but true. I still know companies which haven't invested in moving forward to a new versioning system, because CVS still works good enough. Investments is not only about the hardware and the investigation, preparation and execution of the migration of repositories, but also about the education of the users, for several reasons. -Robert Op Wed, 05 Sep 2012 14:19:31 +0200 schreef Kristian Rosenvold kristian.rosenv...@gmail.com: The hosting bit is defined in context of apache, there is not much we need to do in that respect. This dusussion has been on/off for quite a few years, so I'm not entirely surprised if you haven't seen it all. As for fad, I'm old enough to believe that version control systems have their epochs. No-one is using cvs anymore. This seems to be the decade of git; I'm sure something new shiney will pop up in a few years time. Kristian 2012/9/5 Chris Graham chrisgw...@gmail.com: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
On Wed, Sep 5, 2012 at 8:34 PM, Olivier Lamy ol...@apache.org wrote: [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) +1 (binding) No capacity for volunteering to help :( - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
+1 but have no time to volunteer at the moment. On 9/5/12 6:04 AM, Olivier Lamy wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) GitHub - http://github.com/jdcasey - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
If we applied the same logic back in 2004, we would still be on CVS. Personally, I think Git affords us a lot of opportunity to streamline the contribution process and a much cleaner way of working (patching, rebasing, local branches, etc.) I've switched to Git for all of the rest of what I do, and I have to say that even with the tooling still just maturing even now, Git is far-and-away easier to use. I spend a lot less time juggling working directories, generating patches just to back out something I'm working on at the moment to switch gears for a bugfix, and accepting contributions from anyone is straightforward (especially compared to SVN). I think the world is well beyond simply jumping on the bandwagon with Git; it works well and enables new forms of interaction with the community. We're actually trailing the field by waiting until now to move. I think it's probably prudent, given the size of Maven (and ASF more generally), but we're definitely not riding the cutting edge here. On 9/5/12 8:05 AM, Chris Graham wrote: It's not a matter of thinking that git is like SVN at all. It's the exact opposite in fact; they are different, to the extent that it entails a whole new approach. We have a well resourced, well understood, well supported tool and mature practices with our current SVN. All I am saying is that we really should stop and think as to whether we want to throw that out. I, personally am not convinced. At the end of the day, it's more about WHAT we produce (maven, plugins etc) than the TOOLS (SVN, git, etc) we use. For those who want to use git, fine stick with git SVN, but don't force me to learn a new tool; I do enough of that already. (and I've just come from a project where the personal preferences of a few immature devs forced the abandonment of good mature practices and had Hg shoved down our throats; and this is a $40 Billion dollar company, let's not make the same mistake here). -Chris Sent from my iPhone On 05/09/2012, at 9:41 PM, Arnaud Héritier aherit...@gmail.com wrote: I think Olivier already replied to some points given few points where Git is really interesting : performances, branches management .. But yes there are skills to learn, it's not easy and the error is to think that Git is like SVN But it may be an opportunity to learn ? On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham chrisgw...@gmail.com wrote: -1 Non binding. I have no desire to setup and learn new tools for no clearly apparent advantages. There appears to be multitude of ways that DSCM's can be configured. I'm not sure if sufficient thought/discussion has been given to the way in which it should/can be set up. Where it is to be hosted? My view: Move got a good reason. A fad is not a good reason. -Chris On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: +1. Have no spare time ATM, so cannot volunteer even if I would love to On 5 September 2012 12:04, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) GitHub - http://github.com/jdcasey - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven projects sources to git
I knew someone would misread that. I was not referring to anyone on this list. People on this list are at the pointy end of the stick, although we have a spread of abilities, most are in the upper end of the scale. The reason for this is simple. It's because to do it because we like it, a passion as it were. And that's when you see people at their best. Even with differences of opinion (and experience) such as this. Compare this with the corporate world in which I work. In the quest for the immortal dollar, the bar is being LOWERED, not raised. The average skill level of people is stunningly low. Believe it or not, I _STILL_ have arguments with people as to whether people need to check things in or not. And how to check in, and that you DO need to do an update first, before you commit, and not delete the dir in SVN and then add everything afresh (thus wiping out other people's changes). Sad but true. In this day and age. I was referring 'people of questionable parentage' from my previous project. Several vendors did not have any SCM at all. Fine, give them Hg. But don't force those with mature processes in place to change. Especially when no one has any skills or experience in Hg/git on how/why/etc to set up and manage multiple repos. Even those who were experienced in using GIT, they ended up with hundreds of repos, and it became a real mess to manage. Oh, and stop stupid things like checking built binaries into repos... As robert points out, it's not just the technical reasons for a change that need to be considered, there are all of the other reasons, training, knowledge, support etc that also need to be considered. As someone else points out, if CVS still works for you, fine, stick with it. So, I have a broader view of SCM usage. It's not just the tool being used, it *must* encompass HOW it is to be used. -Chris (who is clearly wearing his SCM hat today... :-) ) On Wed, Sep 5, 2012 at 11:24 PM, Benson Margulies bimargul...@gmail.comwrote: Chris, Just whom amongst us are you labeling 'a few immature devs'? Many of us here have been using both git and svn, extensively, for years now, and have a preference for git based on plenty of practical experience. While git is new-ish at the ASF, it's official, and a growing list of projects are using it Many of the, ahem, outboard components of Maven are in git already. Speaking for myself, I've used svn, I've used 'git svn', and I've used git. Plenty. And it's my considered judgement that git would be better for this project, and I voted as such. Please don't cast asparagus on my by indirectly calling me a cultist. --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [VOTE] Move Maven projects sources to git
+1 I/we can volunteer. -Original Message- From: Stephane Nicoll [mailto:stephane.nic...@gmail.com] Sent: Wednesday, September 05, 2012 9:21 To: Maven Developers List Subject: Re: [VOTE] Move Maven projects sources to git +0 S. On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, 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
Re: [VOTE] Move Maven projects sources to git
+0.5 if it makes devs or patchers lives easier No time to help, and I'd like to see a clearer understanding of how we'll convert non-t/b/t-layout repos before we end up with 50 repositories as others have said. BTW, if anyone is looking at doing that, I found the svn2git worked well for filtering, without having to resort to an svndumpfilter first (I believe it even addresses moves from outside of the subtree's history). - Brett On 05/09/2012, at 4:04 AM, Olivier Lamy ol...@apache.org wrote: Hi, This vote is to decide moving our source tree currently located in one svn repository to git (multiple git repositories). First, we need to have at least 3 volunteers to help on Apache infra for this move and more generally on git Apache infrastructure. (if you are volunteer you must say that with your vote). The vote will pass on majority (PMC committer) and if we have the minimum of 3 volunteers ! BTW contributors can express their opinion by a vote too ! The vote will decide on moving all the source tree (volunteers time will the main throttle). Volunteers will decide on what they move (notification on dev@ is mandatory). The goal is to move simple projects first(scm,surefire, indexer,core, wagon etc..) then plugins (except if Kristian want to start with plugins immediately :-) ) Vote open for 72H. [+1] Move to git scm [0] No interest [-1] don't move to git (please explain why) Thanks, -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
