Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77483 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95898 invoked from network); 22 Sep 2014 20:05:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Sep 2014 20:05:32 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.46 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.218.46 mail-oi0-f46.google.com Received: from [209.85.218.46] ([209.85.218.46:43423] helo=mail-oi0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2E/D2-10955-B0180245 for ; Mon, 22 Sep 2014 16:05:32 -0400 Received: by mail-oi0-f46.google.com with SMTP id i138so4208959oig.33 for ; Mon, 22 Sep 2014 13:05:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jqQmBxRfztItRIMu71FTNfwNVIrJyTjGYsUCxkZRuGg=; b=occ8xikr/z0IZRltQYh6sgwtY9mfkjl+Ia3oHfsRgF7g5zWbVPbS2E0tOmyeST6ahn PGVQCAIdkSnhoVSlI8a0SOoNohJCxfYeMB1DZ1br+hK0i2s755K6y0IyAFICMpzeE+xa g6hGYjS3K7bUg6tu6KsDSVQCWkzsDTGbcUtqLD3Snfx42q7z45vANruL/sGzptzRhbPW S5b3hbAiuBDhaIN/mzHYemMNzZEunY40/ecPamZd2mXg4TeuNpJ7UugyWckzeEdhrP1p 0OT7FNDV6TLrR+9IPMDkRNtaP7oi7abEFS/F3qanlKElhecBdT8FX9gXtTKqavA+6lHM /9xw== MIME-Version: 1.0 X-Received: by 10.60.97.137 with SMTP id ea9mr21866021oeb.12.1411416329003; Mon, 22 Sep 2014 13:05:29 -0700 (PDT) Sender: morrison.levi@gmail.com Received: by 10.76.106.20 with HTTP; Mon, 22 Sep 2014 13:05:28 -0700 (PDT) In-Reply-To: References: <4D27A10E-6EC6-4806-94DB-1BF1B976CA7D@ajf.me> <600A7E27-7E6F-4ECF-805F-D62814AA3AB2@ajf.me> <5420198C.4070209@php.net> Date: Mon, 22 Sep 2014 22:05:28 +0200 X-Google-Sender-Auth: jbh4Zm_nAXUrhCAZxJ9asD3S8V4 Message-ID: To: Pierre Joye Cc: Derick Rethans , Michael Wallner , Peter Cowburn , PHP internals , Andrea Faulds , Laruence Content-Type: multipart/alternative; boundary=089e01161502ebfe090503acf8dd Subject: Re: [PHP-DEV] [VOTE][RFC] Integer Semantics From: levim@php.net (Levi Morrison) --089e01161502ebfe090503acf8dd Content-Type: text/plain; charset=UTF-8 On Mon, Sep 22, 2014 at 3:37 PM, Pierre Joye wrote: > On Sep 22, 2014 3:31 PM, "Derick Rethans" wrote: > > > > On Mon, 22 Sep 2014, Michael Wallner wrote: > > > > > On 2014-09-22 14:08, Andrea Faulds wrote: > > > > > > > > On 22 Sep 2014, at 12:06, Derick Rethans wrote: > > > > > > > >> I would also like to point out that, just like a 8:8 vote is not a > > > >> "50% majority", 16:8 is technically also not a two thirds > > > >> *majority*. The RFC, like with many other important things is of > > > >> course too vague on this. > > > > > > The "+1" is only for 50% majorities. > > > > > > > > > > > An 8:8 vote is not a majority, no, but a 9:8 would be a 50%+1 > > > > majority. > > > > > > > > A 16:8 vote *is* a 2/3 majority. > > > > > > Yes, I think so, too. > > > > I disagree, but the main point was something else. > > Right, but what would be 2/3 of 24 votes for you then? > > > The "voting RFC" should be more clear on this. I don't think it is now. > > It's a pretty vague RFC in the first place, and leaves way too much > > open for interpretation. > > For? # of votes? > I have actually been working with several other people trying to come up with smarter rules for the way we work with RFCs. Undoubtably, confusion about what constitutes a "language change" is a huge issue. To be completely honest, I would prefer that we require 2/3 on all RFCs. PHP is a mature language; if we can't get 2/3 to agree on something it probably isn't good for the whole of the PHP project. I don't want to say anything else here, as technically this is thread hijacking (sorry Andrea) but I am very interested in collaborating with anyone who would like to try to improve the RFC process. Perhaps reply to me off-list if you are also interested. --089e01161502ebfe090503acf8dd--