Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54554 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91220 invoked from network); 12 Aug 2011 19:37:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2011 19:37:09 -0000 X-Host-Fingerprint: 134.29.239.140 140-239-29-134.minnesota.edu Received: from [134.29.239.140] ([134.29.239.140:24595] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A8/50-22613-4E0854E4 for ; Fri, 12 Aug 2011 15:37:08 -0400 Message-ID: To: internals@lists.php.net Date: Fri, 12 Aug 2011 14:37:04 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 References: <4E3F02E8.2050402@sugarcrm.com> <4E450EB1.6090502@lsces.co.uk> <4E456F2F.7030809@sugarcrm.com> <4E45755F.3020005@lsces.co.uk> <4E4578B6.6050708@sugarcrm.com> In-Reply-To: <4E4578B6.6050708@sugarcrm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 134.29.239.140 Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control systemfor PHP (or not). Call for Participation. From: justin.rovang@minnesota.edu (Justin Rovang) GitHub (and Bitbucket) have made forking a social endeavour - it's meant to be a noisy space of code forks for collaboration just as Stas mentioned. Bottom line: *if* a DVCS is adopted - enhancing policies and a process that supports little additional burden on maintainers is required. Having those in place would seem to address the most prudent fear in this conversation. Just because somebody uses DVCS / Github / Bitbucket; doesn't entitle them to anything more than before. It's just another means to collaborate in a more rapid manner; with updated tooling. On 8/12/2011 2:02 PM, Stas Malyshev wrote: > Hi! > > On 8/12/11 11:47 AM, Lester Caine wrote: >>> Pull requests, for one. >> Push/Pull from local copy? > > No, no. Pull requests and push/pull are very different things. Having > people just push whatever they like whenever they like into main code is > what we have now, and it's not really the best way to work on a big > project. Please see on github how pull requests are implemented. > >> The TEAM has a master copy on github or better still git.php.net, but >> you don't >> need 10000 other copies on github as well? I don't like the code >> Drupal produce, > > It's not copies. And yes, I need them - because not every change should > immediately go into master repo. Much better way is to publish it in > your local repo and have it reviewed and then merged into master repo. > Or not. Or merged later. github allows to manage this process better > than storing assorted patches in emails and bugs and pastebin, etc. > >> Sandboxes and development branches are the right way to go, but could >> actually > > Branches are different things than github forks, for different purposes. > Branch is a project, fork is a workspace. You can have multiple people > work on a project, using multiple workspaces.