Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26440 invoked from network); 11 Sep 2013 11:04:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2013 11:04:45 -0000 Authentication-Results: pb1.pair.com header.from=dan@dancryer.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=dan@dancryer.com; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain dancryer.com does not designate 209.85.219.42 as permitted sender) X-PHP-List-Original-Sender: dan@dancryer.com X-Host-Fingerprint: 209.85.219.42 mail-oa0-f42.google.com Received: from [209.85.219.42] ([209.85.219.42:58686] helo=mail-oa0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 76/81-15730-C4E40325 for ; Wed, 11 Sep 2013 07:04:45 -0400 Received: by mail-oa0-f42.google.com with SMTP id n12so9205951oag.1 for ; Wed, 11 Sep 2013 04:04:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dancryer.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=32dVg8Il+W70lbgOX7ptSJtvIKoA7tcYOrwgytEYBwE=; b=N9Ox2CEmfUQK8ev7HegBTT1Xmcq4O5PXZRUett6X9RE+3jRm0DCCDLXVL+ErO/Otpi RwVn0uxZkqxhg534Uju6m77O1ihyvYb9CTIoNWJRBVwjqruWlqxVr05Wh9epCG7ZBq7F qVQkEIDh7RL5LGAl+NEGCFxIHFJh5K/EHD9S8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=32dVg8Il+W70lbgOX7ptSJtvIKoA7tcYOrwgytEYBwE=; b=D1Jxpwq7uv6kbmnkS5jVZgzTKyH7ZQ33p/+YTXZrCA2fkLUIdSQE0s9FKDr2P212kH 6IQNosCl8T5ahs1M4yb0hWzNnjlOAsw/0c3SptHckXHI5w2KlgwGfHsr5M0/+/HqSkQR QoBJmPxxcxNExT8hSTlb8s5MPbPEp1/NNCTOJbtDURtPhWyYGhBzd0DJk7Da4+b3gMwl v5XZrh1KPG44f4yC1f9rSK1UFkKu3Bjqhd3pc3VSznQt1KZfcZt86w5+nxy+L8mu0oCA uBnKhBNIa/Wh6NRCrBZTizTM6px32rZpqSOqGdW5Qqz+QODuFDk0fKeRsGGc2r6CSwfS bsDw== X-Gm-Message-State: ALoCoQmUP1hXNhCegU1OHkc1zgzz51Qfukfeoc7mPtYDUZOIuk2L59+8K9YHujieJufIeHeNaDrg MIME-Version: 1.0 X-Received: by 10.182.81.41 with SMTP id w9mr915747obx.18.1378897481869; Wed, 11 Sep 2013 04:04:41 -0700 (PDT) Received: by 10.60.138.169 with HTTP; Wed, 11 Sep 2013 04:04:41 -0700 (PDT) X-Originating-IP: [213.104.14.230] In-Reply-To: References: Date: Wed, 11 Sep 2013 12:04:41 +0100 Message-ID: To: Florin Patan Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b2e4d7c96bb7004e6199671 Subject: Re: [PHP-DEV] Wake up From: dan@dancryer.com (Dan Cryer) --047d7b2e4d7c96bb7004e6199671 Content-Type: text/plain; charset=ISO-8859-1 Well said, Florin. :) I'm not a core contributor, I never have been and probably never will be as I don't know C... but I do follow internals quite keenly. It strikes me that the biggest problem here is that there's no one entity to decide the rules of the road, so everything (including the rules as to how things should work,) has to be decided by committee - but the committee is too big and too diverse to be useful. If you look at other big open source projects, there's usually a person or group that sets the ground rules for contributions and as long as everyone plays by those rules, contribution is easy, rewarding and painless. Take Blink for example, Google defined the rules but now Intel, Opera, and so on all play nicely together with *very* little friction. Blink seems to have a really good framework for contribution; Instead of X% of contributors having to agree, they provide an "intent to implement" framework to seek feedback on an idea, and an "intent to ship" framework to seek approval from *three* relevant code owners - the people that know the most about the section of code your patch affects. This seems to allow for rapid innovation whilst protecting the codebase from fly-by patches. Could something like that work for PHP? And, perhaps more importantly, would the PHP core contributors be open to a person/group being appointed to lay down these ground rules? It could work on a time-restricted basis akin to the release manager role. --047d7b2e4d7c96bb7004e6199671--