Re: [SVN-MIGRATION] GitHub and ACLs

[email protected] (Travis Swicegood) Wed, 6 May 2009 10:28:12 -0500
Newsgroups svn.migration
Message-ID <[email protected]>
On May 4, 2009, at 12:58 AM, shire wrote:

> I would be fine with this, but I felt that the primary motivation to  
> move to git was git-hub not git itself, as such I don't find it  
> currently compelling enough.  If we want to discuss the differences  
> between git and svn, then I believe that's slightly different. I  
> feel that git is in many ways a more powerful SCM tool, as long as  
> it's not felt as a significant learning difficulty for others who  
> don't currently use it.

As I understood Rasmus, GitHub was mentioned specifically because it  
would allow PHP'ers to not *have* to worry about maintaining the  
repository infrastructure.  Git makes offloading the repo hosting an  
easy choice as we're not tied to them since everyone as there are  
dozens (if not hundreds) of mirrors since each developer has a clone  
of the entire repo history.  GitHub also provides some nice UI tools  
for submitting simple patches (I believe spelling corrections in docs  
was used as an example).

Regardless of GitHub or not, moving PHP to Git would be a plus in my  
book as we maintain multiple branches that need to be kept current.   
SVN's merge tracking (in 1.5.x, the last time I looked at it) wasn't  
all it's cracked up to be.  The argument has been made that everyone  
who uses Git could do so on top of SVN, but because git-svn relies on  
rebasing to work, it becomes much more difficult to share work between  
Git repos.  That pretty much makes each Git repo an island in my  
experience.


> I'm interested in moving off of CVS, regardless of whatever that may  
> be to.  If we move to git-hub I would prefer to see us do it because  
> we feel GIT is the best fit for PHP, not so much that we want the  
> git-hub interface.  Additionally, as I'm eager to get to a newer SCM  
> model, my interest in SVN is significantly tied to getting our  
> partial conversion completed rather than delaying it for movement to  
> another SCM that can easily be bridged to SVN.  Alternatively if  
> we're certain we want to go to GIT regardless of Git-hub, and a CVS- 
> >SVN->GIT route is unnecessarily complicated then we should probably  
> decide to go with GIT now.

Referring back to Rasmus' "Github status" email on April 8th, it looks  
like there's 10 yays, and 3-4 nays. (with you, Brian, as the maybe  
nay).  The nays include some of the (maybe all of the?) largest  
contributors to php-src, so that does seem like a big reason not to  
move.

Either way, I think we'd do well to pick something and move.

-T