Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78691 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49585 invoked from network); 4 Nov 2014 23:59:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Nov 2014 23:59:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.208 imap2-3.ox.privateemail.com Received: from [192.64.116.208] ([192.64.116.208:35443] helo=imap2-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 66/B7-02095-94869545 for ; Tue, 04 Nov 2014 18:59:06 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 2304A8C0084 for ; Tue, 4 Nov 2014 18:59:02 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1wvmWdKypPVk for ; Tue, 4 Nov 2014 18:59:02 -0500 (EST) Received: from oa-res-26-28.wireless.abdn.ac.uk (oa-res-26-28.wireless.abdn.ac.uk [137.50.26.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id B446C8C007D for ; Tue, 4 Nov 2014 18:59:01 -0500 (EST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <6DDFA9F9-EE41-4B53-846D-C771188F2A93@ajf.me> Date: Tue, 4 Nov 2014 23:58:59 +0000 To: PHP internals Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) Subject: RFC Process: Should we hold two different votes? From: ajf@ajf.me (Andrea Faulds) Good evening, A lot of RFCs have been rejected because, while they proposed a feature = people would like, the details were problematic. This has lead to these = features sometimes being considerably delayed. So, in order to do something about this, here=E2=80=99s an idea: Why not = hold two different votes on an RFC, similar to how legislation is passed = in the UK=E2=80=99s House of Commons? The first is on whether the = general principle of the RFC is sound. Once that=E2=80=99s passed, = it=E2=80=99s clear the feature is wanted, so time can then be spent = scrutinising the details of the proposal and making them acceptable. = Then, a second vote can be held, which approves the RFC as a whole, and = its patch (like our current votes do). This way: * Authors know quickly whether a feature has sufficient support (reading = internals doesn=E2=80=99t necessarily tell you anything, as votes and = numbers of positive/negative emails rarely align), without having to = necessarily have done everything before the final vote * Bad ideas are rejected sooner * Good ideas with flawed implementations may succeed in the first vote = and fail in the second, meaning there=E2=80=99s a clear agreement that = it=E2=80=99s wanted but not with this implementation, allowing another = RFC with an improved approach to perhaps be made later Does this sound like a good idea? Thanks! -- Andrea Faulds http://ajf.me/