Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54441
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <slrnj3tulc.6vi.dsp@experimentalworks.net>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>
Date: Sun, 7 Aug 2011 23:55:53 +0200
Message-ID: <CAF+90c-jedkjSQM67q5sMptbWZsrcPnR2O_EDLVuwKq5jK3KvQ@mail.gmail.com>
To: David Soria Parra <dsp@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system for
 PHP (or not). Call for Participation.
From: nikita.ppv@googlemail.com (Nikita Popov)

If a transition from SVN to Git were to be done, the question most
relevant question for me is whether it will be possible to properly
transform the EN-Revision fields in the documentation translation
files. I.e. will we be able to keep the current SVN history (just make
it a Git history) and also automatedly rewrite those EN-Revision
fields to use the appropriate sha1 hashes? I'm all in favor of using
Git, but missing EN-Revisions are really a pain and drastically
increase the time required for updating translations. I would better
keep SVN, if a transformation wouldn't be possible.

On Sun, Aug 7, 2011 at 10:50 PM, David Soria Parra <dsp@php.net> wrote:
> Hi Internals,
>
> Distributed Version Control Systems (DVCS) getting more and more
> popular. In fact they have been discussed within the PHP community and
> on Internals a few times. It came to my attention that more and more
> people like to see PHP move to a DVCS to solve some of the current
> issues (and get other ones).
>
> I was asked to put together a RFC, and so here we are. I've created
> an initial draft. It is mostly based on the very good Python PEP-0374.
> It compares Git and Mercurial.
>
> =A0 =A0https://wiki.php.net/rfc/dvcs
>
> There are reasons for choosing these systems:
> =A0 * Both are quite popular
> =A0 * I know them
> =A0 * Most PHP devs that I know, know at least on of them
> =A0 * Big projects have recently moved to them, they have
> =A0 =A0 similar requirements like PHP
>
> The RFC is far from done, so please help me finishing it and get it out.
>
> This is a call for participation to help to get a (probably heated)
> discussed started and work on the RFC to make it good enough to finally
> choose a system or, and that is a valid option, stay with SVN.
>
> So if:
> =A0- you are interested in DVCS
> =A0- know a little bit about PHPs requirements for a DVCS
> =A0- are not a fanboy
>
> Feel free to discuss this and add your thoughts to the RFC. I would
> love to not do this on my own. Feel free to catch me on IRC (dsp_ on
> php.pecl) and discuss it.
>
> NOTE: this is not the place for any religiouise discussion about git vs
> mercurial whatsover. if you have nothing else to add than "hg is $***
> anyway" or think hosting platform XY will solve all our problems
> without reading the RFC carefully, please post to alt.relgion.* and not
> here.
>
>
> - David
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>