Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91025 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24578 invoked from network); 30 Jan 2016 19:37:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2016 19:37:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=joe@joeconstant.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=joe@joeconstant.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain joeconstant.com from 209.85.220.54 cause and error) X-PHP-List-Original-Sender: joe@joeconstant.com X-Host-Fingerprint: 209.85.220.54 mail-pa0-f54.google.com Received: from [209.85.220.54] ([209.85.220.54:36541] helo=mail-pa0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CC/C0-19320-9011DA65 for ; Sat, 30 Jan 2016 14:37:45 -0500 Received: by mail-pa0-f54.google.com with SMTP id yy13so59063427pab.3 for ; Sat, 30 Jan 2016 11:37:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joeconstant-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JcpXyrXuU+F5a2d2svX3DbGSQcTgE3aZ7mc+j+edW6k=; b=OzVIN5hedAtGWMxwiK+1wilgunzLi0aQP0KrDkARTVHA1v2+DnDfUOtmlwizigqI3W Rktwfbu7sWz9HecpLLzlvDTysv4HetEkjGfr6HHbq1EvEK5ORxkDkoEPpUL/N2CIMex1 MgCMuhDWxqpbJacFOxDwkdE47S+t5mXCDNlVS+VwUcLAiVFNh7TiUCuPaJ9i3MKvO4V3 VOauD4sX3ztbZskUMAZyLo5PEp3ihaHCaQyFANKAGPqgBSnCII201Etk2BCGbEDBNTKM XeROGt4J7ezrbGZ7kWNZqy4rkCWi4T0Pz5ej4F+Eimu/XhrcXl3fVE2jeB5HTWaQe/s8 JRLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=JcpXyrXuU+F5a2d2svX3DbGSQcTgE3aZ7mc+j+edW6k=; b=U/TzW2Y52gnT4Gi/BZIzmqLNahlCVsjAehJWSlDYRYuJn3cW6G/32Q0DTLRHDofldp 051tdx6/LhMMXZB9oGK2n5RIAyJPdZ3fkG6i7l7Rk3cRpOcFNwH/n7leU6B7RvhFQ5eD 1o8o3+s4+N3Q8xT4JB6TmoqJaL67z7HpTo3y/HHX3fi3zxhRigKIj7GTrAw1j2AI8TQ8 IKHU/7jORpIVPYPjAGuDZeviyzOWiVJv7j+hZkFH8mu8WaNHn1rjY/W7IyEuW65e7+AD +knN0sU5kw5PpNP8t3LH58mfUdpk7zUzuYpexpNxokD9iNzavv18rBemZUUEH7qFTzJl 9OYA== X-Gm-Message-State: AG10YOQSWezVV1MU0XSVufBvWjIHtnws6H3VixaT5rKBoGEK/RXIBY7Moa1hxnAXeqmYtg== X-Received: by 10.66.150.66 with SMTP id ug2mr25032674pab.114.1454182662880; Sat, 30 Jan 2016 11:37:42 -0800 (PST) Received: from [192.168.2.8] (96-19-55-246.cpe.cableone.net. [96.19.55.246]) by smtp.gmail.com with ESMTPSA id th10sm32203252pab.3.2016.01.30.11.37.42 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 30 Jan 2016 11:37:42 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-5F880444-CD71-48B0-973C-594B38A0BEE5 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (13D15) In-Reply-To: Date: Sat, 30 Jan 2016 12:37:41 -0700 Cc: Andrea Faulds , PHP internals list Content-Transfer-Encoding: 7bit Message-ID: References: <6F.D4.55829.C14FCA65@pb1.pair.com> To: Jakub Zelenka Subject: Re: [PHP-DEV] Should we rethink the 50%+1 requirement for non-"language changes"? From: joe@joeconstant.com (Joe Constant) --Apple-Mail-5F880444-CD71-48B0-973C-594B38A0BEE5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable >>P.S. Please don't top post... ;) I'm not trying to thread hijack. Just trying to add to the discussion. The o= ps post was in regards to RFCs passing to easily. My contention with the low= voter turnout is in line (or at least intended to be in line) with that.=20= >> It's often a specific feature for extension so moving everything to PECL i= s not really an option. My argument is that if it affects core, a certain percentage of voting membe= rs (people that have taken on the responsibility of directing the future of c= ore) should be required to vote. I understand that they may not be intereste= d, but if the voter turnout is really that low, the proponents should be doi= ng more to drum up interest rather than simply allowing an RFC to pass.=20 Joe Constant On Jan 30, 2016, at 12:14 PM, Jakub Zelenka wrote: On 30 Jan 2016 18:07, "Joe Constant" wrote: > > As someone who has never participated with intervals before and only just r= ecently subscribed to the list, I would like to see a minimum percentage of v= oting members participating in a vote for something to pass. In my interpret= ation of the current rules, a measure could pass with only 3 votes cast (2 f= or / 1 against). In fact, there was a recent proposal that passed with only 1= 1 votes cast. If that few of voting members are participating, maybe the pro= posal wasn't clear enough (or maybe it's just not needed at all)? Sure you c= an argue that they had ample time to discuss, but I would say perhaps they j= ust saw no value in it. If a proposal isn't offering enough value for the gr= eater community, maybe it doesn't belong in core and should be either a pecl= extension or userland code? > I disagree with this. The fact that not many people voted doesn't mean that t= he feature is not important. Some RFC are very technical and about specific= topics that not many voters is interested in. However it can be important f= or some users and shouldn't be rejected just because there are not enough vo= tes even if the majority is in favour. It's often a specific feature for ext= ension so moving everything to PECL is not really an option. P.S. Please don't top post... ;) Cheers Jakub= --Apple-Mail-5F880444-CD71-48B0-973C-594B38A0BEE5--