Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54974
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <0C.17.12710.C0AB75E4@pb1.pair.com>
To: internals@lists.php.net
Date: Fri, 26 Aug 2011 10:21:39 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
References: <slrnj5appg.6vi.dsp@experimentalworks.net> <CAJW__o3+=Bai6xj2fR7dNdZVn60WW=RKzBCO3k+HBvo8V7R-fw@mail.gmail.com>
In-Reply-To: <CAJW__o3+=Bai6xj2fR7dNdZVn60WW=RKzBCO3k+HBvo8V7R-fw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Choosing a distributed version control systemfor
 PHP
From: justin.rovang@minnesota.edu (Justin Rovang)

Now hold on a sec - It's ok to vote to determine the fate of PHP 
development - for the entire PHP-lovin' world.

Yet, it's not ok to vote for the handful of developers to collaborate?

Three weeks of discussion (based on what I've seen here on the list) 
seems not enough for such a heavy change.

Point in case - it's still being discussed right here; right now. But I 
agree with the direction: try the contenders out.

I understand there's complications such as scripts and automation, but I 
hope they aren't the reason for impeding progress.

Sticking with a system for 'a long time' results in just as many battle 
scars - if not more than keeping up with the times (conservatively).

On 8/25/2011 1:12 PM, Kalle Sommer Nielsen wrote:
> 2011/8/24 David Soria Parra<dsp@php.net>:
>> 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.
>
> I won't transfer the discussion over here but; I don't want to move to
> a new system we we did it just a few years ago, as Rasmus said long
> before we moved was that we want to find a solid system that could
> hold out just as long as the old setup. I don't have a problem by
> using SVN, nor merge as we have been good at keeping files in sync so
> its easy to merge patches, much easier than the old unicode-trunk.
>
> That being said; I agree with Stas that having a vote is not a good
> way to actually make a choice here, but it gives a hint of those that
> voted, as I'm sure that there are many more actively working on the
> project like PEAR. PECL and Doc guys thats not gonna vote because they
> don't follow Internals.
>
> But -1 from me.
>
>