Re: [SVN-MIGRATION] GitHub and ACLs
| From: | Philip Olson | Date: | Thu, 07 May 2009 01:55:13 +0000 |
| Subject: | Re: [SVN-MIGRATION] GitHub and ACLs | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | svn.migration |
| Request: | Send a blank email to svn-migration+get-334@lists.php.net to get a copy of this message | ||
On 6 May 2009, at 14:33, Rasmus Lerdorf wrote:
The point would be to see if we had a unanimous desire to move. We didn't. I really hate making decisions on things I am not going to be working on heavily myself, but I think we have been stalled on this for too long now, and we should do something, anything, at this point. So, since I don't think we are that far away from having a working Subversion repository, I say we finish that work. Github as-is isn't where we need it to be yet anyway. I still want to keep an eye on it, and we should be looking at ways to separate our code repository from our authentication system and the various other bits and pieces that are driven off of the CVS password file today. One thing I wanted to do years ago was to set up php.net as an OpenID provider. If we can get that up and running, then a future move to Github (which supports OpenID), or some other mechanism, would be simpler.Being closer to having unanimous desire before moving to a dvcs [git] sounds reasonable. The status quo is CVS and the SVN motto was "CVS done right" Should we tackle the authentication problem before or after the move to SVN? Ideally before but after is understandable and more likely. A general php.net authentication idea has been posted here: - http://wiki.php.net/ideas/phpnetauth I'm sorry to report that the doc team is not yet ready for this move, and we'll report back on this later. Knowing that we've chosen one (SVN) helps. Regards, Philip