I'm fine with git and I think moving to something like that together with up-to-date tools to contribute (or review patches etc.) will help a lot.
But I would prefer to keep the (core) infrastructure at PHP internally. It's just *so* much easier to integrate tools, add things like hooks for the bugtracker or whatever. Having people develop part of a project on github then is surely fine - but php-infrastructure would still be the "official core" imho. In this discussion I previously mentioned the TYPO3-community (which I guess stand for a lot of others) who integrated a review-system based on gerrit into their forge (actually a RedMine-based system; including bugtracker etc.) And that integration has helped a lot - both in openness/ease of use as well as actually "getting the job done". It looks like the basic vote goes in the git-direction - first step taken :-) But I hope we'll find a wise decision on how to further continue in this matter afterwars. PS: Thank you all for your time and work in this matter. Regards, Stefan On 08/25/2011 09:08 PM, Ilia Alshanetsky wrote: > If we do decide to make a VCS change the vote should be fairly one > sided for "option of choice" as this has a fairly broad impact on our > development process. > > On Wed, Aug 24, 2011 at 5:03 PM, David Soria Parra <d...@php.net> wrote: >> Hi Internals,, >> >> after 3 weeks of discussion, I think we are ready to start voting on >> the DVCS RFC. If you think something is missing or should be explained >> in more detail, let me know. >> >> Votes can be found here: >> >> https://wiki.php.net/rfc/dvcs/vote >> >> The RFC can be found here: >> >> https://wiki.php.net/rfc/dvcs >> >> Voting will be opened for 2 weeks and end on Sept. 7 at 12 pm. >> >> - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
