Re: [RFC] abolish narrow margins

On Thu, Jul 12, 2018 at 12:11 PM Stanislav Malyshev <smalyshev@gmail.com> wrote: > > Hi! > > > Things which don't effect the language, but are more of a question of > > preference - e.g., the decision to name phpng as PHP 6 vs PHP 7 - or for > > that matter, deciding about a different release cadence. It's one thing to > > That's one of the places where 50% or plurality vote would be > appropriate - when we have binary (or n-ary) choice for some decision > that has to be taken. We don't want to end up in an absurd situation of > not choosing any name or any release date because none of the options > has 2/3. So in this situation, I think we go with the majority or > plurality (in case of multiple options) vote. > > -- > Stas Malyshev > smalyshev@gmail.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php I think for n-ary votes we need a different system. Only being able to cast one vote with winner takes all has a lot of downsides. I'm not sure what distinguishes binary votes that only need >50%. I don't think as simple as whether or not there is code involved; for example changing our RFC processes and such should require more agreement than that.