Re: Re: Keeping CVS? was - Re: [PEAR-DEV] CVS 2 SVN (Re: [PEAR-DEV] candidatesfor PEAR Group: why should we vote for you? Tell us your plans and
yourhistory)

Agreed on all points. I know know Chris, but Scott and I are fellow authors, so I have a bit of an in there. I've managed to secure both the pear and pear2 user for our use, one for the old legacy code and another for the new pear2 5.3 code. The idea that I've been kicking around is that each package would be created independent of those accounts until its an official package. At that time, the PEAR Group would create a real repo for the pear2 user and pull in the lead's work. The lead and maintainers would all be given permission to write to the official repository, but true to the nature of a distributed VCS developers would be encouraged to use their own repositories for experimentation and keep the official ones clean of all code that's still experimental. Another plus for GitHub is that it shows who's working on a given project in their own repositories as well, so its easy for other devs to pull in experimental changes if they want to run them as well. -T On Jun 23, 2009, at 11:07 AM, Joe Stump wrote:

Huge +1 from me. I've moved all of my PEAR projects to GitHub. Git+GitHub make managing FOSS projects SO much easier. No more manual patch submissions: just fork mine, commit, and I'll merge. So easy. If we do happen to go this route we might want to consider mandating a central PEAR account has access to repositories there? (I did this with my Google Code projects before moving to GitHub). Finally, I know Chris and the guys at GitHub well enough to be a liaison if needed. Love, love, love this idea. Love. <3 and such. --Joe On Jun 23, 2009, at 9:02 AM, Travis Swicegood wrote:

Funny you should mention Git. For those of you following the SVN migration for php-src, you'll have seen Rasmus' idea of moving php-src to GitHub. We're working on setting up a playground on GitHub to experiment. There's a ton of pluses going this route. Some are Git specific, some are specific to GitHub: * Fully distributed - now people can commit at conferences when wifi is down! -- I'm looking at you David Coallier. :-) (git) * Globally distributed back-ups. Each developer has a full copy of the repositories history. (git) * We're letting people who dig managing VCS servers manage ours instead of us tinkering with it. (GitHub) * Really easy, no software required patch submission. You can edit a file directly on github.com. (GitHub) * Seamlessly enables the incubator/sandbox model coupled with official releases that we've talked about for pear2. Want to start a new package? Create a project on GitHub and let pear-dev@ know about it, then propose creating an official repo for it once it's ready to go beta. We'll have a playground up in a few days for everyone to play with. I should stress that at this point we're still just toying with the idea. There seems to be a movement afoot in php-src to move to Git in the long-term, so this could be a good opportunity for PEAR to blaze the path. :-) -T On Jun 22, 2009, at 10:51 PM, Kazuyoshi Tlacaelel wrote:

This is great, I think this is great, this is great! Joshua has been providing a very reliable svn server for the pear-community thanks Joshua! am really happy, about this. and really want to see pear running on svn. (at least) or git (as a must) Trully I think we should draw a milestone/deadline and announce it on the pear site, for the next scm big change! and have everybody migrate according to that! This is really nice! On 2009/06/23, at 11:07, Greg Beaver wrote:

Alan Knowles wrote:

Are we still keeping CVS?, I'd rather keep using it for my packages. I use svn mounted dav for development locally, and commit them into CVS (unfortunatly it does not work with SVN to SVN commits). I dont mind deleting the svn code and putting a place holder to 'see cvs.php.net' in the folder?

Hi Alan, cvs.php.net is actually being shut down (unless my understanding is off) and replaced with svn.php.net Greg --PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

--PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

--PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php