Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76096 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40804 invoked from network); 25 Jul 2014 08:11:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jul 2014 08:11:12 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.52 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.52 mail-qa0-f52.google.com Received: from [209.85.216.52] ([209.85.216.52:35704] helo=mail-qa0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4D/87-29475-E1112D35 for ; Fri, 25 Jul 2014 04:11:11 -0400 Received: by mail-qa0-f52.google.com with SMTP id j15so4040162qaq.25 for ; Fri, 25 Jul 2014 01:11:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=zY/hnIJey+8qSNbij83HY3GSalqQ/8LZkBmWOQNiJU8=; b=VuACeDv4JHJ3iI/91E33NwURNVgezGafkfua9u65LV2F+SKPvmJVRTnDPSu0FwcN+Z HTsTYrl3G/AUrNFRxrq7U0Gjc9UJNR+wbhMd9u1aodHA+1Wiuw7n0UhmWBie3Ia3q40y +jpZ8+nq5g4gis7oGp+num3P1YzPy8YyTyU8A7gG55FY47Us1bksMFEJj/OESY8MHalT WpCuJr5rzrKPBNReSkzDcMOdyjLUuf64fNp/BAOS2C2ApuDa75MM4oHHW3eN0gSk8oRx qRfV4QdVqVjtbrYyO5kqBZsW+WjGoWBFiEjcXPboVcwc0F+O8gzZH5vrnx4cBoev+zv2 EvHw== MIME-Version: 1.0 X-Received: by 10.140.87.75 with SMTP id q69mr23371926qgd.94.1406275873830; Fri, 25 Jul 2014 01:11:13 -0700 (PDT) Received: by 10.140.24.54 with HTTP; Fri, 25 Jul 2014 01:11:13 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Jul 2014 10:11:13 +0200 Message-ID: To: Zeev Suraski Cc: Kris Craig , Yasuo Ohgaki , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: Move phpng to master From: pierre.php@gmail.com (Pierre Joye) On Fri, Jul 25, 2014 at 9:51 AM, Zeev Suraski wrote: > On Fri, Jul 25, 2014 at 7:28 AM, Kris Craig wrote: > >> >> >> > While this is a major change to the language implementation, it does >> not actually affect end users in any meaningful way except for the posit= ive >> =E2=80=98side effect=E2=80=99 of their apps running faster. So while we= believe that >> technically a 50%+1 vote should suffice, we hope to get well over 2/3. >> >> If you're not going to delay this, then you should at very least clarify >> the wording in this section. You believe 50%+1 should suffice but hope = to >> get well over 2/3. So is the *required* majority 50%+1 or 2/3? >> > > The text I put there is exactly what I think about the subject of require= d > majority. 50%+1 is enough for a change that does not effect end users in > any meaningful way, but I'll be happier if it received a 2/3 majority to > leave any doubts away. It affects users, it is a total rewamp of the engine, it requires 2/3. I fail to understand to see yet another attempt to discard simple RFC rules. > I should also point out that, according to the Voting RFC, whether or not >> an RFC "actually affects end users in any meaningful way" is NOT a facto= r >> in determining whether a 2/3 supermajority is required or not. Here's w= hat >> it actually states: >> >> > For these reasons, a feature affecting the language itself (new syntax >> for example) will be considered as 'accepted' if it wins a 2/3 of the >> votes. Other RFCs require 50% + 1 votes to get 'accepted'. >> >> Since the phpng RFC already acknowledges that it affects the language >> itself, this is clearly a 2/3 requirement situation. Whether it affects >> end-users or not is irrelevant. Under current rules, your RFC must have >> 2/3 support in order to pass. >> > > As the person who wrote that text in the Voting RFC, I can tell you with > absolute certainty that you are 100% wrong in your interpretation, as I'v= e > said numerous times in the past. > A feature that affects the *language* itself is not a feature that affect= s > the *language implementation*. It affects both, there is no point to argue. > I updated the section to be fully technical and removed my wish of heart = to > get a 2/3 majority. Although I'd still very much like to get > 2/3, it's > not required. It is. Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org