Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54594
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error)
Message-ID: <4E48331F.1080403@lsces.co.uk>
Date: Sun, 14 Aug 2011 21:42:07 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>	<CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com>	<4E3F02E8.2050402@sugarcrm.com>	<alpine.DEB.2.02.1108121119420.4043@whisky>	<CAH-PCH4YO1e-+=+38DrhwUe-nR9akJ+c=64vk0ar3GZGM5YOmw@mail.gmail.com>	<4E450EB1.6090502@lsces.co.uk>	<4E456F2F.7030809@sugarcrm.com>	<4E45755F.3020005@lsces.co.uk>	<4E4578B6.6050708@sugarcrm.com>	<4E45A2BD.7060506@lsces.co.uk>	<4E45AFDF.9000001@sugarcrm.com>	<4E45B6A9.9080607@lsces.co.uk>	<4E46F26E.1000607@garfieldtech.com>	<4E4784E7.9050700@lsces.co.uk> <CAMWw8k99xGxp8CtyAB8TtUQt1gfE85ghwQoVH2xH7d6u8bk8zQ@mail.gmail.com>
In-Reply-To: <CAMWw8k99xGxp8CtyAB8TtUQt1gfE85ghwQoVH2xH7d6u8bk8zQ@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: lester@lsces.co.uk (Lester Caine)

Gwynne Raskind wrote:
>> The only real disadvantage to hg is having to handle python code to maintain
>> >  it, people might start converting from PHP;)  Although phphgadmin is a start
>> >  to improving the php interface support and could be a good start at a fully
>> >  PHP managed interface to a PHP repo?
> I'm starting to think we should take a cue from Linus and just do as
> we did with bugsweb, newsweb, and so forth: Build our own
> (Hg/Git-compatible) DVCS from scratch!
>
> (I'm joking... mostly.)
It's not such a silly idea ... In reality both git and hg get modified to 
provide custom facilities, so creating at least a clean php based front end to a 
DVCS engine makes perfect sense. Especially if it links in with bugsweb and 
perhaps highlights hotfix or other patch information directly in the code base? 
Commits tag the relevant bug report automatically? And patch accepts both hg and 
git inputs for those without karma, or would commit for those with?

I have been more than happy with hg working into git repos I did simply assume 
that there would be an extension for git to handle hg in the same way, but it 
would appear not? As far as I can tell from the hggit extension, mirroring the 
git information is not particularly difficult, so a 'hybrid' that could provide 
both hg.php.net and git.php.net views seems practical, and commits need to be 
managed via karma, so processing that should not be difficult? But the problem 
area I still see is the handling of submodule/subrepo commits where they cross 
several submodules ... that was an area where custom scripts used to exist for a 
couple of the projects I work with and I think THIS may be an area where a 
scratch built interface may be a possible option.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php