Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90610 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30700 invoked from network); 13 Jan 2016 15:12:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jan 2016 15:12:20 -0000 Authentication-Results: pb1.pair.com header.from=pmjones88@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pmjones88@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.173 as permitted sender) X-PHP-List-Original-Sender: pmjones88@gmail.com X-Host-Fingerprint: 209.85.160.173 mail-yk0-f173.google.com Received: from [209.85.160.173] ([209.85.160.173:36555] helo=mail-yk0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3B/E3-10601-25966965 for ; Wed, 13 Jan 2016 10:12:19 -0500 Received: by mail-yk0-f173.google.com with SMTP id v14so397891389ykd.3 for ; Wed, 13 Jan 2016 07:12:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i035aYiqrNp9xEQrwppy41WCUyL0Sjpqcm54jrsH9nw=; b=tL8iPWqI9QbdTbe9xlEOxFEB1p6yKfy/YFqNbYyP/DUmrYMoiZ8PcrapoI6ICNCmZN RNki3dIHWQUmnVNQTUo9tZGgVgQcUCeKz/SYnWWnUTyHxwLauxNKPrpXu5649IOS4A04 SR8VDW3/IzNSOyk1ChGBTw3PhdjE00hd59focmXchfdL0r+dZ61ndJK4ldU05JRTtbto fucJcriDTVqXh8BWZRqUOJdw5B2pCvsbWz5lOxSoo3gF5l8Vc84jwfpszwLkONxAQj5p s88LGaAT01bO43MgkaNwvwda8cdoXWzGtt2NLrLg3BVWU9JoAa8xS7WxIZj5rIFR1mZb F1Dw== 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=i035aYiqrNp9xEQrwppy41WCUyL0Sjpqcm54jrsH9nw=; b=jKtWsvIxZi1wHtrV7Cz6gOkKFIloQUAo3iZdI1E6zr5sAt9DLcLBUq1zLm81tCKSJc jIqHLNE3BYsqGNk3PD4K044douX9tJvXZtM2MWiSrp4ZuLuhkYJ+gn+la4lsiSrfJayI p+nEnUBmNpG2HtNwHhliK3oEF0KeulFLwCJKASTOUsqOmRuab8Inyk0frjOgxVNEBnXk SjYPShltKoe0K3DjYkcjc4VbzUT0le/HklVU67g4eSSwA8eWGZad5hhG6gn61ijKzNaK Y0MLh8YCiiAOJvYSXM2aXLs3qdbTF81Ah3PPHO5bzpR+nfyehmKLlpKOZDvADsmXmwjC KxHw== X-Gm-Message-State: ALoCoQlBCQ6P/ebdTs5fKF/BLyodOPKZFQyxH/KstNK8x5YAbamlOisUFTMBcHYh6KJi2QppZKXYZli8dEhqkeu2Q8RRtvtn8Q== X-Received: by 10.129.92.132 with SMTP id q126mr113972871ywb.46.1452697935699; Wed, 13 Jan 2016 07:12:15 -0800 (PST) Received: from ?IPv6:2602:306:cecb:ae30:5072:f28:8516:6cc9? ([2602:306:cecb:ae30:5072:f28:8516:6cc9]) by smtp.gmail.com with ESMTPSA id 204sm1034089ywz.39.2016.01.13.07.12.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 13 Jan 2016 07:12:14 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) In-Reply-To: Date: Wed, 13 Jan 2016 09:12:13 -0600 Cc: John Bafford , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <3CB02F5A-A02F-4976-9B62-07AECA75372A@gmail.com> References: <8B865D2A-6762-430D-9EA1-9B693DE8E8C3@zort.net> <56948002.1080802@gmail.com> To: Zeev Suraski X-Mailer: Apple Mail (2.3112) Subject: Re: [PHP-DEV] Internals and Newcomers and the Sidelines (WAS: Adopt Code of Conduct) From: pmjones88@gmail.com ("Paul M. Jones") Hi all, > On Jan 12, 2016, at 17:07, Zeev Suraski wrote: >=20 > Out of 45 approved RFC, 34 would have cleared a 90% bar, 35 would have = cleared an 85% bar, and 38 would have cleared a 75% bar. >=20 > To the best of my recollection, all of the RFCs that generated major = storms fall in the these 7 RFCs that cleared the 67% mark, but failed = the 75% mark. >=20 > Very importantly, out of the RFCs that cleared 85% and 90% - none had = more than 5 people opposing, most had 0, and most of the rest had less = than 3. >=20 > It's also worth noting that once you clear the 75% mark, you're very = likely to also clear 85% and 90%. Only 3 RFCs cleared 75% and didn't = clear 90%. >=20 > What I'm getting at is this: >=20 > Most passed RFCs are manage to gain something that's very close to = consensus, way higher than 2/3, with barely a handful of people = opposing. >=20 > If the vote is close to 2/3 - there are very high chances that the RFC = is controversial, that people who oppose it will be opposing it = passionately, and that as civilized as we try to be - bad vibes are = likely to ensue. This is a very interesting analysis, and I find it appealing. An alternative interpretation might be: "As people feel an RFC is near = the pass/fail point, they argue it more vociferously." That's more ... = dynamic? ... interpretation, in that it doesn't matter where the = pass/fail point is (2/3, 3/4, etc); conversational volume increases = around that point wherever it is. When the perceived support is much = higher, or much lower, than the pass/fail point, the conversational = volume decreases. That's an untested hypothesis, of course. If it's true, though, it means = that raising the bar to 4/5 means conversational volume will increase = only for RFCs that already have very high support, which is probably not = the intended consequence of raising the bar. --=20 Paul M. Jones pmjones88@gmail.com http://paul-m-jones.com Modernizing Legacy Applications in PHP https://leanpub.com/mlaphp Solving the N+1 Problem in PHP https://leanpub.com/sn1php