Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100568
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
References: <CAESVnVoiqHxycJ6CDGQm8hXipVZV-a=MD78D2sV7pSXOSnKgvA@mail.gmail.com>
Message-ID: <9f1b9af5-291f-66c6-b895-ff2deb22971c@gmx.de>
Date: Wed, 13 Sep 2017 23:25:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVoiqHxycJ6CDGQm8hXipVZV-a=MD78D2sV7pSXOSnKgvA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC][Discuss] Increase non-syntax runtime-impacting RFC
 votingthreshold to 60%
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 13.09.2017 at 22:42, Sara Golemon wrote:

> https://wiki.php.net/rfc/rfc.voting-threshold
> 
> This topic has come up on the mailing list a few times, so I'd like to
> formally open the topic for discussion.
> 
> I'm generally pretty liberal when it comes to allowing the PHP
> language to evolve and explore its identity, but the truth is a
> feature that has 30 people vote against it and 31 people vote in favor
> of it is not a mandate by any stretch of the imagination.  It's an
> opportunity to examine why a divide exists and if we're all being
> honest with each other, improve the original idea before it becomes a
> maintenance burden.

Thanks for taking the initiative on this!

FTR: Zeev has also started preparing an RFC which includes this voting
threshold, besides further issues: <https://wiki.php.net/rfc/voting2017>.

> Please note the "Open Question".  I'm not all that sure 60% is enough
> of a mandate either, but I wanted to be conservative in my
> conservatism.  If folks think 2/3 is more appropriate (and consistent
> with syntax changes), I'm happy to change this number before we move
> to voting phase.

IMHO, a 2/3 majority would be most suitable for any changes to php-src.
Most votes have even been clearer, and I believe most (if not all) which
would have failed a 2/3 threshold would have failed 60% as well.  (Zeev
presented more detailed stats on this list a while ago.)  Having a 2/3
threshold for all php-src change related votes would at least avoid the
discussion into which category the vote falls, though.

-- 
Christoph M. Becker