Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93315 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94310 invoked from network); 13 May 2016 14:26:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 May 2016 14:26:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:39252] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 80/04-01216-724E5375 for ; Fri, 13 May 2016 10:26:49 -0400 Received: from [127.0.0.1] (unknown [82.240.16.115]) (Authenticated sender: flaupretre@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPSA id D9D6D2003BE; Fri, 13 May 2016 14:17:01 +0200 (CEST) To: Rowan Collins , internals@lists.php.net References: <1d8d5c0c-0403-7e9e-5b93-56de43648c99@php.net> <7119991e-415f-20e3-22e8-5f6a68df0e34@gmail.com> Message-ID: Date: Fri, 13 May 2016 16:26:40 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <7119991e-415f-20e3-22e8-5f6a68df0e34@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 160513-0, 13/05/2016), Outbound message X-Antivirus-Status: Clean Subject: Re: [PHP-DEV] [RFC] [Discussion] Third-party editing of RFCs From: francois@php.net (=?UTF-8?Q?Fran=c3=a7ois_Laupretre?=) Le 13/05/2016 à 15:30, Rowan Collins a écrit : > If somebody adds something that is genuinely irrelevant (e.g. based on a > simple misunderstanding of the RFC) then somebody else (*anyobdy* else) > could remove it. Maybe I am not candid enough but do you imagine what it could become on a controversial RFC like STH ? What does 'genuinely irrelevant' mean ? Will you accept that someone deletes your comment because he finds it 'genuinely irrelevant' ? Of course not. So, we'll end up with a system where anybody can write anything and nothing can be removed. IMHO, we touch the limit of what can be done with a bare wiki. Another way to solve this need would be to authorize voting as soon as discussion starts and allow an explanation comment to be associated with each vote. People could modify their vote and the associated comment while discussion runs, and it would be easy at any time to get a snapshot of the current trend and a resume of the raised arguments. This would also allow RFC authors to know better why people were voting the way they did, something that was requested several times in the past. Unfortunately, I don't know if we can associate a free comment with the voting tool we're using. This could require writing a new vote app. Regards François