Re: An Experiment with GIT
On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? Ok, here's the goods: http://git.sonatype.org/ The instructions and links are there on the page and I've enables the git protocol. You can browse via the web but the git protocol is just way faster. If there are people who want to goof off at work and work on Maven I would be happy to serve it up via http so you can get through your nasty corporate firewall. Regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Works like a breeze :) Thanks for the effort. -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Hi Jason! first, both thumbs up! The main reason why it's hard to get used to git is because most people work with centralised CVS-like VCS systems since decades and git is completely different. But getting used to git only takes a few weeks and after that one will never switch back (if he is not forced by the company). Now my question: Is this git repo up to date, or at least will it be in the future? Are the main users using git from now on, or are there still people pushing their changes to SVN directly and you have to do git-svnimport or git-svn from time to time? txs, strub --- Jason van Zyl [EMAIL PROTECTED] schrieb: On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? Ok, here's the goods: http://git.sonatype.org/ Wissenswertes für Bastler und Hobby Handwerker. BE A BETTER HEIMWERKER! www.yahoo.de/clever - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 3 Oct 07, at 2:34 AM 3 Oct 07, Mark Struberg wrote: Hi Jason! first, both thumbs up! The main reason why it's hard to get used to git is because most people work with centralised CVS-like VCS systems since decades and git is completely different. But getting used to git only takes a few weeks and after that one will never switch back (if he is not forced by the company). Now my question: Is this git repo up to date, or at least will it be in the future? Yup, I'll rebase frequently but really based on feedback from people a little heads up I will rebase at will if necessary. This is the first experiment but I see that 28 people have cloned the one of the GIT repositories so I imagine I will just automate something. But I would like to try a few cycles of people cloning, me pulling into a work branch, merging and syncing back to Apache before we go hog wild. I'm going to put the legal muck in there as well. Before the first merge back can happen any code grants and relinquishing all right to Apache must happen as part of this process. Are the main users using git from now on, or are there still people pushing their changes to SVN directly and you have to do git-svnimport or git-svn from time to time? SVN will be the source of truth at Apache for quite some time I imagine. It's only me so far and it's really to facilitate people working effectively who do not have direct access to our SVN repositories. txs, strub --- Jason van Zyl [EMAIL PROTECTED] schrieb: On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? Ok, here's the goods: http://git.sonatype.org/ Wissenswertes für Bastler und Hobby Handwerker. BE A BETTER HEIMWERKER! www.yahoo.de/clever - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 10/3/07, Jason van Zyl [EMAIL PROTECTED] wrote: Ok, here's the goods: http://git.sonatype.org/ Would it be possible to add wagon? Thanks, Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 3 Oct 07, at 12:23 PM 3 Oct 07, Jochen Wiedmann wrote: On 10/3/07, Jason van Zyl [EMAIL PROTECTED] wrote: Ok, here's the goods: http://git.sonatype.org/ Would it be possible to add wagon? I would but someone seems to have removed the 1.x branch. Ah, who removed the 1.x branch? Thanks, Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 3 Oct 07, at 12:23 PM 3 Oct 07, Jochen Wiedmann wrote: On 10/3/07, Jason van Zyl [EMAIL PROTECTED] wrote: Ok, here's the goods: http://git.sonatype.org/ Would it be possible to add wagon? Done. http://git.sonatype.org/ Thanks, Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 3 Oct 07, at 1:09 PM 3 Oct 07, Jason van Zyl wrote: On 3 Oct 07, at 12:23 PM 3 Oct 07, Jochen Wiedmann wrote: On 10/3/07, Jason van Zyl [EMAIL PROTECTED] wrote: Ok, here's the goods: http://git.sonatype.org/ Would it be possible to add wagon? I would but someone seems to have removed the 1.x branch. Ah, who removed the 1.x branch? It's back to the trunk, so that's what I'll publish. Thanks, Jochen -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 10/3/07, Jason van Zyl [EMAIL PROTECTED] wrote: I would but someone seems to have removed the 1.x branch. Ah, who removed the 1.x branch? Knowing myself, I'd tend to plead guilty, but fortunately I haven't got the permissions ... :-) -- Look, that's why there's rules, understand? So that you think before you break 'em. -- (Terry Pratchett, Thief of Time) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Jason van Zyl wrote: On 30 Sep 07, at 12:23 PM 30 Sep 07, Mauro Talevi wrote: This is a comparison with SVN I've found on the Git site: http://git.or.cz/gitwiki/GitSvnComparsion But one of the main issues IMO is the integration with IDEs - it took quite a long time for SVN to catch up to CVS standards. Until an analogous level is available for Git, how many will be willing to consider trading in the ease of development for the advantages it may offer? We're not going to be using GIT at Apache. In this case it's use GIT versus mail patches. I don't expect a landslide of people using this method, just the most determined and those who understand that using an SCM while working on their changes is a good idea. There is just no way to work like this with SVN, it was just not designed to work like this. Some one who is not a committer cannot incrementally check in their changes so the existing IDE integration doesn't help in this regard. There is someone working on an Eclipse GIT plugin, but anyone wanting to use the standard SVN diff and attach patches to JIRA can continue to do so. It's not like it's one or the other. Well - if the proposal is of an optional layer that sits on top of SVN and provides easy branching for patch submission/tracking, then yes it seems OTOH something really worth exploring. Once the Git infrastructure has been set up I'd be up for taking it for a spin. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Ok, everything seemed have loaded over night. I'll now work on publishing and setting up webgit. On 1 Oct 07, at 4:23 AM 1 Oct 07, Mauro Talevi wrote: Jason van Zyl wrote: On 30 Sep 07, at 12:23 PM 30 Sep 07, Mauro Talevi wrote: This is a comparison with SVN I've found on the Git site: http://git.or.cz/gitwiki/GitSvnComparsion But one of the main issues IMO is the integration with IDEs - it took quite a long time for SVN to catch up to CVS standards. Until an analogous level is available for Git, how many will be willing to consider trading in the ease of development for the advantages it may offer? We're not going to be using GIT at Apache. In this case it's use GIT versus mail patches. I don't expect a landslide of people using this method, just the most determined and those who understand that using an SCM while working on their changes is a good idea. There is just no way to work like this with SVN, it was just not designed to work like this. Some one who is not a committer cannot incrementally check in their changes so the existing IDE integration doesn't help in this regard. There is someone working on an Eclipse GIT plugin, but anyone wanting to use the standard SVN diff and attach patches to JIRA can continue to do so. It's not like it's one or the other. Well - if the proposal is of an optional layer that sits on top of SVN and provides easy branching for patch submission/tracking, then yes it seems OTOH something really worth exploring. Once the Git infrastructure has been set up I'd be up for taking it for a spin. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Hello, Could you publish the git repository address ? Regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? I'm just setting it up on a reliable server and I will get it out shortly. Regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? I moved everything over to a Contegix box where it can be supported and they are just updating Subversion and install the necessary Perl libraries required for the initial git-svn setup. Should be done shortly and I would prefer this then using a box I have sitting in my office. I would like this to work so I'll put it on a 24/7 supported server I have at Contegix. Should be done shortly. This will be fun. Are you mostly interested in plugins or the core? I will publish them as separate GIT repos so I'll do the ones people are most interested in first. Trying to jam everything into one GIT probably doesn't make sense if people are going to focus on particular things. The other thing I want to setup is a strategy for dealing with the legal. So if people work on branches of their own, it is really no different then mailing me a patch or putting it in JIRA. But I would like to be a little more rigorous as given the interest (6 people mailed me so far) the branches that I may pull must have any legal bits in there like code grants and I want them in a standard place and named consistently so I can process them easily. As I pull in changes from people I can log the code grant along with reviewing the code and merging it. I want this to be easy but must provide the right legal framework. I'll probably just put the right files in the svn repo so that when you clone the repo you have the template, can fill it in, name it accordingly and then I'll see it when I merge. Regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
So Contegix is starting the process, and SVN needs to be upgraded on the servers to support git-svn and they are starting now. They should be done in two hours, and then I will clone and publish the repo. So let's aim for tomorrow to publish them. I'll find the right legal goop to make available for people wanting to attempt this. On 30 Sep 07, at 11:04 AM 30 Sep 07, Insitu wrote: Hello, Could you publish the git repository address ? Regards, -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Jason van Zyl wrote: Hi, For anyone who wants to make changes to Maven but doesn't have access I am going to setup a GIT repository to try and enable some distributed development. After using GIT for about a week I'm having a hard time using SVN but obviously we're not going to be switching anytime soon. But for anyone who has patches or wants to try and work with me to get changes in I am going to try this method of publishing Maven as a GIT repository which will allow anyone to clone the repository and work on any changes you like in a controlled way. Once you clone you can commit changes to your own copy of Maven and do whatever you like. Then in order for me to see your changes I can simply pull from your originally cloned repository to a branch on my side and merge. Merging is sooo easy with GIT. So easy in fact that it makes you wonder how SVN got it so wrong and makes it so painful compared to GIT. This is the model that the Linux kernel uses where anyone has a real copy of the repository, they work as they like, creating branches for features of what have you. I am trying this with Oleg Gusakov who has many ideas and is helping me do some experiments with the artifact resolution system. But anyone else who is interested in trying just let me know. This document is the most helpful: http://utsl.gen.nz/talks/git-svn/intro.html And a little collection of things I have read about GIT: http://del.icio.us/jvanzyl/git It is so damn fast it is unbelievable. With the visual tool that comes with it you can see the entire history of the project in a few minutes. It is very, very cool. I simply cannot believe how easy it is to merge bits from all over the place. My hope is that this method being truly distributed means that people can work on their branches in a way that's natural and we remove the immense tedium working with patches. If you have something good, it's now very easy for me to pull a branch from you and try it. If that branch works it then takes me a second to merge it. I test and them push back to subversion using the git-svn bridge. In the short term I really only want to try with a few people but if you're keen, want to learn about GIT (which I highly, highly recommend) then I will take your patches. I think any developer here and anyone who has ever tried to contribute changes sees that the JIRA+patch model is highly unworkable and bordering on completely useless. JIRA might be fine to raise the issue but with a reference to a GIT repository to pull from it will make life infinitely easier. People who are not committers can work with people that are in a way that resembles everyon being part of the team. Dealing with patches just sucks ass and as a result we don't look at them nearly as often as we should so I hope this can become a model that enables people to contribute in a more effective way. I'm going to try this with Oleg but I am highly hopeful. I will help anyone who wants to try this as I see this as a way to truly collaborate with the community. Down with JIRA+patches! All hail JIRA+GIT! :-) This is a comparison with SVN I've found on the Git site: http://git.or.cz/gitwiki/GitSvnComparsion But one of the main issues IMO is the integration with IDEs - it took quite a long time for SVN to catch up to CVS standards. Until an analogous level is available for Git, how many will be willing to consider trading in the ease of development for the advantages it may offer? Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
Jason van Zyl [EMAIL PROTECTED] writes: Are you mostly interested in plugins or the core? I will publish them as separate GIT repos so I'll do the ones people are most interested in first. Trying to jam everything into one GIT probably doesn't make sense if people are going to focus on particular things. Maybe there should be one git repository per directory under https://svn.apache.org/repos/asf/maven/ ? Thanks for the trouble anyway. I have started using mercurial and git this year and I am far from being an expert, but I greatly appreciate the freedom those tools provide, and most importantly the ease of branching and the ability to version your changes locally. One thing I found very interesting too are patch stacks, using mercurial queues or stgit. They are great to keep your changes focused ! I look forward to news about that and still hope to have some times for not only reading but also writing :) -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: An Experiment with GIT
On 30 Sep 07, at 12:23 PM 30 Sep 07, Mauro Talevi wrote: This is a comparison with SVN I've found on the Git site: http://git.or.cz/gitwiki/GitSvnComparsion But one of the main issues IMO is the integration with IDEs - it took quite a long time for SVN to catch up to CVS standards. Until an analogous level is available for Git, how many will be willing to consider trading in the ease of development for the advantages it may offer? We're not going to be using GIT at Apache. In this case it's use GIT versus mail patches. I don't expect a landslide of people using this method, just the most determined and those who understand that using an SCM while working on their changes is a good idea. There is just no way to work like this with SVN, it was just not designed to work like this. Some one who is not a committer cannot incrementally check in their changes so the existing IDE integration doesn't help in this regard. There is someone working on an Eclipse GIT plugin, but anyone wanting to use the standard SVN diff and attach patches to JIRA can continue to do so. It's not like it's one or the other. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
An Experiment with GIT
Hi, For anyone who wants to make changes to Maven but doesn't have access I am going to setup a GIT repository to try and enable some distributed development. After using GIT for about a week I'm having a hard time using SVN but obviously we're not going to be switching anytime soon. But for anyone who has patches or wants to try and work with me to get changes in I am going to try this method of publishing Maven as a GIT repository which will allow anyone to clone the repository and work on any changes you like in a controlled way. Once you clone you can commit changes to your own copy of Maven and do whatever you like. Then in order for me to see your changes I can simply pull from your originally cloned repository to a branch on my side and merge. Merging is sooo easy with GIT. So easy in fact that it makes you wonder how SVN got it so wrong and makes it so painful compared to GIT. This is the model that the Linux kernel uses where anyone has a real copy of the repository, they work as they like, creating branches for features of what have you. I am trying this with Oleg Gusakov who has many ideas and is helping me do some experiments with the artifact resolution system. But anyone else who is interested in trying just let me know. This document is the most helpful: http://utsl.gen.nz/talks/git-svn/intro.html And a little collection of things I have read about GIT: http://del.icio.us/jvanzyl/git It is so damn fast it is unbelievable. With the visual tool that comes with it you can see the entire history of the project in a few minutes. It is very, very cool. I simply cannot believe how easy it is to merge bits from all over the place. My hope is that this method being truly distributed means that people can work on their branches in a way that's natural and we remove the immense tedium working with patches. If you have something good, it's now very easy for me to pull a branch from you and try it. If that branch works it then takes me a second to merge it. I test and them push back to subversion using the git-svn bridge. In the short term I really only want to try with a few people but if you're keen, want to learn about GIT (which I highly, highly recommend) then I will take your patches. I think any developer here and anyone who has ever tried to contribute changes sees that the JIRA +patch model is highly unworkable and bordering on completely useless. JIRA might be fine to raise the issue but with a reference to a GIT repository to pull from it will make life infinitely easier. People who are not committers can work with people that are in a way that resembles everyon being part of the team. Dealing with patches just sucks ass and as a result we don't look at them nearly as often as we should so I hope this can become a model that enables people to contribute in a more effective way. I'm going to try this with Oleg but I am highly hopeful. I will help anyone who wants to try this as I see this as a way to truly collaborate with the community. Down with JIRA+patches! All hail JIRA+GIT! :-) Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
