Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55299 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5142 invoked from network); 8 Sep 2011 06:36:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Sep 2011 06:36:24 -0000 Authentication-Results: pb1.pair.com header.from=dukeofgaming@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dukeofgaming@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.174 as permitted sender) X-PHP-List-Original-Sender: dukeofgaming@gmail.com X-Host-Fingerprint: 209.85.161.174 mail-gx0-f174.google.com Received: from [209.85.161.174] ([209.85.161.174:62165] helo=mail-gx0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/82-05788-662686E4 for ; Thu, 08 Sep 2011 02:36:23 -0400 Received: by gxk21 with SMTP id 21so732961gxk.33 for ; Wed, 07 Sep 2011 23:36:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YQCtKilLXNQgbW7aC3Q7xwGIym0JOKdweKd9OWbNn6s=; b=QnDcFFKOz1Ld12NpkVgiRkQ0/tzzUPissYuAJGcfKlGm0VR38p0SevyHeenpv9daLm XcGSpUpoYpTw6miw6Z1viNp5AQiUrArs1iHW3eIc+vqsmsbn2bIQZJZyiq5uI0hoK44c wAvzOe78KmJo/B7GbkdxFIJ/QbzWXAXBMBRqU= Received: by 10.100.208.3 with SMTP id f3mr260729ang.62.1315463780195; Wed, 07 Sep 2011 23:36:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.107.13 with HTTP; Wed, 7 Sep 2011 23:36:00 -0700 (PDT) In-Reply-To: <4E685E53.40908@php.net> References: <4E685E53.40908@php.net> Date: Thu, 8 Sep 2011 01:36:00 -0500 Message-ID: To: Rasmus Lerdorf Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=001636848296555e3804ac684735 Subject: Re: [PHP-DEV] [RESULT] Choosing a distributed version control system for PHP From: dukeofgaming@gmail.com (dukeofgaming) --001636848296555e3804ac684735 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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 th= e "master" repository, however, given the social impact these services have =97specially github=97 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 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 th= e > > 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 > > --001636848296555e3804ac684735--