Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54438
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.193 as permitted sender)
Message-ID: <4E3F02E8.2050402@sugarcrm.com>
Date: Sun, 07 Aug 2011 14:26:00 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "RQuadling@GMail.com" <RQuadling@GMail.com>
CC: David Soria Parra <dsp@php.net>, 
 "internals@lists.php.net" <internals@lists.php.net>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net> <CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com>
In-Reply-To: <CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system
 for PHP (or not). Call for Participation.
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

On 8/7/11 2:13 PM, Richard Quadling wrote:
> There will be (not might be, but will be), multiple, and potentially
> conflicting/incompatible, versions available. Which do I choose? If
> everyone is capable of forking PHP, which is the official one? In the
> event of a single official repo, then why bother with a DVCS? (I'll
> admit I'm naive on the true requirement of DVCS, as I think SVN works
> very well).

You can build single-source workflows around DCVS too. The fact that 
everybody is keeping the copy of the history doesn't mean there can't be 
one "main" repository. The point of DCVS is not as much in doing 
different things from what we're doing now as doing roughly the same 
things in a better way - more efficiently.

> The main thing I'm worried about is if feature X splits the core devs
> so much that there are 2 competing repos, both with a significant
> number of core devs supporting each repo, how do I choose which is
> which? If my abilities include being able to code at the core level,
> which should I support? Both? All 3, 4 or 10 different forks?

This can happen right now - take the code, put it on any of the hosting 
facilities and declare yourself the new king of PHP. DCVS changes 
nothing here. It's the process that defines the workflows, not the 
technology. Technology just makes the workflows easier to execute.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227