Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90574 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30258 invoked from network); 12 Jan 2016 19:29:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Jan 2016 19:29:46 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.82.49 mail-wm0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:36389] helo=mail-wm0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/B6-27877-82455965 for ; Tue, 12 Jan 2016 14:29:45 -0500 Received: by mail-wm0-f49.google.com with SMTP id l65so265564959wmf.1 for ; Tue, 12 Jan 2016 11:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=T+OOFUnmVVMRAL/L+FhbXI9a4HUr2Ma3PA+pvBQHnxg=; b=QPMyIrOFLL7lhP0e6yFhUeP+JDO6/ouaw8omDXuxgGlzlpRWG7a9SuRmhfSjVUta5Z A8QZAw4gKqCskloeOnvRKIFujjkXMV+as69vlkUBkC/QYs9slIxyizl8bvEr1bgqbOls 8yYqGN+SmxPH6pFe4VCzL1aVD2xLpvdS/j8OmCWAXaslY7E9Fsv+9zGE99vbizEWNtoo 3qlI8y58uc9e2m3jneq7m8VJR+Juys722vAsk/lKD7UD+Zn6pBmUT9iAGZqDE2zdhEhC 5paC6N3ScXwbR0iRQIN6p4wUFVzjZfV0HP2T3Glwgtp+aRW11HxXh/wcXGiCuAVdsiFN qRug== MIME-Version: 1.0 X-Received: by 10.194.94.138 with SMTP id dc10mr61458864wjb.37.1452626981823; Tue, 12 Jan 2016 11:29:41 -0800 (PST) Received: by 10.27.86.202 with HTTP; Tue, 12 Jan 2016 11:29:41 -0800 (PST) In-Reply-To: <56952323.5030201@php.net> References: <5690BCE6.6010908@gmail.com> <569182FD.6070404@gmail.com> <56918458.1070101@gmail.com> <5691D2EA.1050808@gmail.com> <5692307D.5050900@lsces.co.uk> <56925977.1040801@dennis.birkholz.biz> <5693C027.4070804@eliw.com> <5694D270.3050109@dennis.birkholz.biz> <56950882.7020008@eliw.com> <56950BB4.7040400@heigl.org> <56952323.5030201@php.net> Date: Tue, 12 Jan 2016 20:29:41 +0100 Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: Dan Ackroyd , Andreas Heigl , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7bb03d4e3e350f052928130e Subject: Re: [PHP-DEV] Re: Anonymous voting on wiki From: tyra3l@gmail.com (Ferenc Kovacs) --047d7bb03d4e3e350f052928130e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 12, 2016 at 5:00 PM, Fran=C3=A7ois Laupretre wrote: > Le 12/01/2016 15:52, Dan Ackroyd a =C3=A9crit : > >> Fran=C3=A7ois Laupretre wrote: >> >> I would like the process to be amended to disable posting >>> opinions/discussions about an RFC while the vote is open, >>> considering there was enough time for that during the >>> discussion phase. >>> >> >> This is not a good idea. >> >> That won't actually make people discuss a proposal during the discussion= s >> phase. >> >> Instead people will be voting with the conversation about the proposal >> not being complete. >> >> And then we'll be stuck with bad decisions. >> > > Well, it was just a suggestion. What I want to avoid is people jumping in > when vote starts and asking for fundamental changes. Each time it happene= d > to me, I had to stop the vote, modify the RFC, and restart the whole > process. This also caused a pair of RFC not to be included in PHP 7. Some > of them are even abandoned because I am quite tired of such behaviors. > > I'm OK with the discussion *going on* during the vote but I'm looking for > a solution to a real problem. > yeah, that(discussion only seems to happen after introducing the voting phase) is frustrating for the rfc author, but that is the last phase where complaints can be voiced and most people have a tendency to defer stuff until the last minute, that sucks, but not specific to our project, and don't know what can we do about it. some of those last minute feedback are actually useful, so if we are looking for the best solution it i better to have those concerns to be raised and heard even if late than ignored and voted on a flawed proposal. I think one possible countermeasure can be to start the voting as soon as the discussion dies down (while still keeping the minimal discussion period) instead of waiting for more feedback arbitrarly and getting frustrated that it only comes after one puts the rfc up for votes. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --047d7bb03d4e3e350f052928130e--