On Monday 27 April 2009 01:29:45 am Don Brown wrote: > > While Atlassian still uses Subversion, I've moved over to using Git > for all my work and personal projects, and I've found it a much better > tool to keep me productive (great branching/merge, sane cli, > super-fast, etc). However, why I'm particularly excited about having > a Struts mirror is I hope it will be a way for the community to be > much more active in its development. With Subversion, only committers > can make any changes, so if you as a user wrote a feature, all you can > do is attach it to JIRA and hope for the best. If you are more > adventurous, you could fork Struts into your own Subversion repo, but > then you have to deal with the pain of keeping them in sync. Git, as > a distributed SCM tool, is built for this type of decentralized > development, and in particular, Github makes it easy to track, both > for the user and committer. > > In a perfect world, we'd have an "official" Github mirror of Struts. > If a user wanted to get rid of OGNL, they can click the "Fork" button > and have their own repo. Once they commit their changes, they send us > a pull request or at least create a JIRA issue and link to their repo. > What is cool about this is the user can start using their feature > now with minimal hassles keeping up to date with Struts trunk, but > better yet, any other user can fork that fork and build on that > change. You could have a whole sub-community around a certain fork, > say, one that gets rid of OGNL and all other Struts deps, all without > any need to have commit access. As Struts committers, it allows us to > take our philosophy of letting the community sift through ideas to the > next level from just ideas and JIRA issues to actual code and forked > releases. Our job then is to pick the creme of the crop, vet the > legal stuff, and push the chosen features back to the official Struts > repo. > > Therefore, I think git will help us empower our community, make the > committers lives easier, and deliver better code quicker. Who could > argue with that? :) > > Don
Philosophically, I can see what you're saying, but I was perusing the intarwebz to _see_ what the differences are... Here is what appears to be a nice run-down of a few really good reasons - http://markmcb.com/2008/10/18/3-reasons-to-switch-to-git-from-subversion/ But, another huge thing for me... I am constantly doing things like - find . -name pom.xml | grep -v '.svn' | xargs grep 'xwork' (whereas, when I used to use CVS, I could have just done - find . -name pom.xml -exec grep 'xwork' {}\; ) After reading up on Git a bit and noticing right away that there are no more hidden '.svn' directories, I'm sold. :) (I'm an easy sell) -Wes -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
