Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102818 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27483 invoked from network); 14 Jul 2018 00:45:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jul 2018 00:45:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=levim@php.net; sender-id=unknown Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.50 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.215.50 mail-lf0-f50.google.com Received: from [209.85.215.50] ([209.85.215.50:43293] helo=mail-lf0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/4A-39793-C97494B5 for ; Fri, 13 Jul 2018 20:45:17 -0400 Received: by mail-lf0-f50.google.com with SMTP id m12-v6so28471265lfc.10 for ; Fri, 13 Jul 2018 17:45:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cLi24qZNed4o3yZ1HgJsKjs94UDxareEi59TdL8msAA=; b=CQtNTD9BQWpLFLPBTPEaCl7gfl4hC3gl25eLv3PPf0whfOszpwZd5YVnE55eJlPi5l EgfA37HfykzBDVsGCJElOeBqECxWxCRsRT5R9Sd7E0p8ywDGXRYEYfBxL49k7tIM+aaU z0JK3E651mc9nnnzCvh34NndqHOb+1u+ok0uhd+tFwokoX5WB6DCNl/tWMeJwpL76XBC afBBRAuFG3tu9jVvNSgGMlSQHJRiU/g/bnil+jxXbl3kBjK51kTYv1f+ChmTtm4W90TE vi82alGAd/1+APvNnh5dqRdJXBOV512snwNcJNrGCM6YWVShgFc8xGecfbeEtr6mmGAD vDVA== X-Gm-Message-State: AOUpUlHr7Lnr8m8SAX4ySUUFd7JfTE/bLtMC9YyNta4h41GS+09/oAoC f7YvoyooLuqnRJ6NN4FeOXngF9OsyRwic1tv8QQ= X-Google-Smtp-Source: AAOMgpeLvdKhvZZERRGA8xggVBcA3cwjHFC8lHS3gldCbFrFMdcPIYusNYSK822edKyPpnd9knMUUw9a9+Hlq9FUlSw= X-Received: by 2002:a19:d313:: with SMTP id k19-v6mr6172436lfg.29.1531529113668; Fri, 13 Jul 2018 17:45:13 -0700 (PDT) MIME-Version: 1.0 References: <38809703-3aa1-34cf-82b9-019ee8788cb9@gmx.de> <58.E2.57182.05E864B5@pb1.pair.com> In-Reply-To: Date: Fri, 13 Jul 2018 18:44:59 -0600 Message-ID: To: Stas Malyshev Cc: internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] abolish narrow margins From: levim@php.net (Levi Morrison) On Thu, Jul 12, 2018 at 12:11 PM Stanislav Malyshev 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.