On Fri, Aug 26, 2011 at 2:28 AM, Ferenc Kovacs <tyr...@gmail.com> wrote: > On Fri, Aug 26, 2011 at 8:48 AM, Lester Caine <les...@lsces.co.uk> wrote: >> David Muir wrote: >>> >>> FWIW, PEAR is already moving to GitHub. >> >> So who dictated that .... >> There should at least be a little consistency in PHP and this is just >> another example of everybody just doing what they want and sod the rest of >> us :(
PEAR is very different than the core. PEAR is inherently split up into small sub-packages that are easily maintained using separate version tracking. You could say PEAR is much like PECL, but there are still plenty of differences. We have a group of elected officials which (mostly) make final decisions, and we also have many individual developers that like to do what they want with their libraries. PEAR developers have long been able to use other publicly available version control systems. Yes the main repo has been with PHP, until svn.pear.php.net was set up for PEAR2 and subsequently moved back to PHP infrastructure once svn.php.net was set up. Just in the past few months or we've moved all of PEAR2 to git, and PEAR packages are individually moved over at will. > the pear group decided that obviously. > btw. I thought that only the pear2 infrastructure (site, packages) are > moving to github. PEAR2 was the first, yes. For PEAR(1) our QA team has focused on unmaintained packages. It takes a lot of manpower to vet new contributors by requesting patches and building enough trust that we're OK granting them svn.php.net access. We've recognized that it's easier to get new/external contributions on github, which is very important when maintainers leave and our QA team has to take over. -- Brett Bieber -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
