Yup, I know, actually I've just finished reading the RFC's implementation part and saw github just mentioned here and there, but not being the point of focus, which is the most correct attitude to have IMHO while choosing a DVCS (that's the only way Mercurial can steal some of the DVCS thunder: github out of the way, hehe).
The question is, now, will github be part of the integration workflow?, or is that yet to be discussed?. I imagine the project wants to retain governability and I applaud that instead of using a 3rd party service as the "master" repository, however, given the social impact these services have —specially github— I think github must at least be part of the workflow, because, you know, the repository is distributed now, no place is necessarily special. Anyhow, what is the next step?, how could one help?. Regards, David On Thu, Sep 8, 2011 at 1:18 AM, Rasmus Lerdorf <ras...@php.net> wrote: > On 09/07/2011 11:15 PM, dukeofgaming wrote: > > Awesome news, this particular decision tends not to be an easy one in > open > > source software communities (well, perhaps now it is easier with all the > > traction git & github have) so I think this is evidence of how good the > RFC > > process is. > > > > Is there a github repository already?. > > Note the vote was for git, not github. And yes, there has been a github > repo for a long time: https://github.com/php/php-src > > -Rasmus > >
