Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54517 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95155 invoked from network); 12 Aug 2011 10:26:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2011 10:26:47 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:38570] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/48-40016-4EFF44E4 for ; Fri, 12 Aug 2011 06:26:45 -0400 Received: from localhost (xdebug.org [127.0.0.1]) by xdebug.org (Postfix) with ESMTPS id 7E849DE142; Fri, 12 Aug 2011 11:26:41 +0100 (BST) Date: Fri, 12 Aug 2011 11:26:41 +0100 (BST) X-X-Sender: derick@whisky To: Stas Malyshev cc: "RQuadling@GMail.com" , David Soria Parra , "internals@lists.php.net" In-Reply-To: <4E3F02E8.2050402@sugarcrm.com> Message-ID: References: <4E3F02E8.2050402@sugarcrm.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system for PHP (or not). Call for Participation. From: derick@php.net (Derick Rethans) On Sun, 7 Aug 2011, Stas Malyshev wrote: > On 8/7/11 2:13 PM, Richard Quadling wrote: > > 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. But you can't call it PHP anymore due to the license, where as with a DCVS with people having forks on publically accessible repositories, everybody is basically violating the license. I share Richard's concerns about finding out "what is the real one"/best one/latest one. Most recently I found that out with two related PHP projects: https://github.com/preinheimer/xhprof vs https://github.com/facebook/xhprof and: https://github.com/corretge/xdebug-trace-gui or https://github.com/beberlei/xdebug-trace-gui or http://www.rdlt.com/xdebug-trace-file-parser.html regards, Derick