Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74286 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46597 invoked from network); 17 May 2014 18:43:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2014 18:43:41 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain zend.com from 209.85.128.180 cause and error) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.128.180 mail-ve0-f180.google.com Received: from [209.85.128.180] ([209.85.128.180:59701] helo=mail-ve0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/A0-43080-CDDA7735 for ; Sat, 17 May 2014 14:43:41 -0400 Received: by mail-ve0-f180.google.com with SMTP id db12so4581988veb.25 for ; Sat, 17 May 2014 11:43:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Pyy8A++XsIYJXgFp19Rh/UikwqCZnpXLI89Ab+RNFF8=; b=I1pREq3XJU5GZYbTaj6Fe/+ONcT0/CfhtXVuD6dSGuXkFlro/hbhxpCQCu39U3GAPq gfr51j4sBkTwBhbgos5EveL+6q8szYo4DT5rXFRs/5fvYV1HPIzK5BneHOc7UaUygQG8 V1GBDTOXXKwlqr2yVZHsOGjvnT6OZuFqNpPim6TtNuIv4lw2LkLOX+BgkQYYlNobuq3q h53cUIQ7+dECSNia3Hn3c7opC8dAtLExZqMBbevqIK2M5WWk0GOekEqG6VeNp8sCPHfA 6bNzhWt+AGQpygLjN5CfGTxDIEsw6uf9WZxuZP5oUhLKYKZN5/HDHz4j+og3Q0IDeDgC 3DLg== X-Gm-Message-State: ALoCoQkTmTSIxAoCoTEz2CEYMhRad2dG/aB4hb2zAC02CXrjqUr2PnHWnfP+OdvAZn0iq4jpgWW9EUhwRgU7891fjy//eZmyXhxL4tBL3zRObJd0arlrR9ZV1V0R6DxYAufanu7/y0dc X-Received: by 10.58.30.1 with SMTP id o1mr8027357veh.37.1400352218235; Sat, 17 May 2014 11:43:38 -0700 (PDT) References: <3939936079205827190@unknownmsgid> <2422EE67-5206-4A27-9175-3C738A9128C9@ajf.me> <4081130594864738388@unknownmsgid> <-9104174845926653435@unknownmsgid> <7E5AB5FE-20F1-4C94-A64D-9D04CED99350@chalopin.fr> In-Reply-To: <7E5AB5FE-20F1-4C94-A64D-9D04CED99350@chalopin.fr> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKfhLjt84gHtgksioRAK1c4y3wh6QFJUsxrAfv8WSUCQFaQTQIO8522A1SuagCZTal4YA== Date: Sat, 17 May 2014 21:43:29 +0300 Message-ID: <56558f11ebd9940b4e281000240dfc1a@mail.gmail.com> To: bruno@chalopin.fr Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: RE: [PHP-DEV] A call for help (urgent) From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: bruno@chalopin.fr [mailto:bruno@chalopin.fr] > Sent: Saturday, May 17, 2014 9:31 PM > To: PHP internals > Subject: Re: [PHP-DEV] A call for help (urgent) > > > Le 17 mai 2014 =C3=A0 18:03, Zeev Suraski a =C3=A9crit : > > > But much > > like I wouldn't dream of telling the docs team how they should do > > their job, I don't expect the opposite to happen either. > > So if I understand you suggest that only core developers should decide for core > modifications ? Isn=E2=80=99t it against the voting RFC which you=E2=80= =99re one of the authors ? It may be against what=E2=80=99s written there (which is why I need to beg = as opposed to just point people to it) - but not its spirit. The voting RFC was written with language functions, features and processes in mind. Not implementation. Things like Traits - which most certainly involves Core, or return type hinting - these are the things the Voting RFC was created for. As you pointed out, I'm one who those who wrote much of the text of it, I should know. I didn't even dream that we'll have RFCs that deal with low-level implementation up for vote. If I did, there'd be a separate dedicated section for it. > That=E2=80=99s a really weird vision of an open source community for me. It actually isn't. Open Source is typically some form of meritocracy, and those who have merit in a given component are those who own it. The RFC process was designed to give a wider range of 'stakeholders' a say in the language direction - and I think it greatly helped PHP in the last few years. However it was never designed to give those stakeholders a say about its implementation. Unfortunately, I wasn't sufficiently forward-looking to make that clear in the RFC. I still think this can work without changes to the Voting RFC, again, assuming people do not vote on implementation RFCs that don't directly concern the parts of the code they own. Zeev