Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77485 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98898 invoked from network); 22 Sep 2014 20:12:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Sep 2014 20:12:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=florian@margaine.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=florian@margaine.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain margaine.com from 209.85.213.169 cause and error) X-PHP-List-Original-Sender: florian@margaine.com X-Host-Fingerprint: 209.85.213.169 mail-ig0-f169.google.com Received: from [209.85.213.169] ([209.85.213.169:37147] helo=mail-ig0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E9/83-10955-0A280245 for ; Mon, 22 Sep 2014 16:12:16 -0400 Received: by mail-ig0-f169.google.com with SMTP id l13so4564034iga.2 for ; Mon, 22 Sep 2014 13:12:13 -0700 (PDT) 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:from:date :message-id:subject:to:cc:content-type; bh=BWSO/qjrvDS2aw3/xHSOAwyiML8nvg9XppWkJ7s23j0=; b=iMx3p92JDlOni/W9IX1FSF14lcbEgaRYZsFhJJDXc+EHbP2rIAJoTiOrYfAPgUT+XU H8n9VgFCIJLsmckYkTWPgcUiR/gXnUFMT6gThbSmfWwQ2NLTQenR1JxNqSGVSnlhcgb9 60sNblXDtVz9MgxIMRJUjsFVklmw7dTKGZVlOaCYCtez8Oz6e5jZ8mGXkTuWGjLabi8V 2CPc66KuKZ1cIl6sq0+QvsystDSUBK95UJWWzOQBwShJU/v3/tij9WSKnE7OxMO7lDeC BXSvZ8a4CzryOq7ytdY4cIvdbAWmlLU1DL5740WK0IE7GuNC26QyBwfkT1BUFnkl99cL cM7A== X-Gm-Message-State: ALoCoQlwK0wLg32pa4wydbNiFuSnhsxtGZ6EFTtlQw+cCSmoMrRnuUkPdy8/ixkd+OgHgyYxN8SB X-Received: by 10.50.122.70 with SMTP id lq6mr16905029igb.8.1411416733730; Mon, 22 Sep 2014 13:12:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.41.20 with HTTP; Mon, 22 Sep 2014 13:11:53 -0700 (PDT) X-Originating-IP: [89.92.205.106] 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:11:53 +0200 Message-ID: To: Levi Morrison Cc: Pierre Joye , Derick Rethans , Michael Wallner , Peter Cowburn , PHP internals , Andrea Faulds , Laruence Content-Type: multipart/alternative; boundary=089e015383340c29bc0503ad110f Subject: Re: [PHP-DEV] [VOTE][RFC] Integer Semantics From: florian@margaine.com (Florian Margaine) --089e015383340c29bc0503ad110f Content-Type: text/plain; charset=UTF-8 Hi, Just a side remark: from an external point of view, it seems like you need an application to handle the RFCs. An application with a strict business logic, which leaves no ambiguity as to when and how an RFC should be valid. The "what" is more ambiguous however, and I'm not sure as to how it should be handled. Regards, *Florian Margaine* On Mon, Sep 22, 2014 at 10:05 PM, Levi Morrison wrote: > 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. > --089e015383340c29bc0503ad110f--