Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93316 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96453 invoked from network); 13 May 2016 14:48:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 May 2016 14:48:56 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.45 mail-wm0-f45.google.com Received: from [74.125.82.45] ([74.125.82.45:35317] helo=mail-wm0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3E/54-01216-759E5375 for ; Fri, 13 May 2016 10:48:56 -0400 Received: by mail-wm0-f45.google.com with SMTP id e201so25721317wme.0 for ; Fri, 13 May 2016 07:48:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=RL81rvvs/Gml0RB4nK/uZiakZMpnEEuvvcoEBU8Kgyk=; b=wNCIUxurXQ6ug5BeDd0u3y1zGGyEvDZmcx7yuf23T5H7ALJxWO0bvKWLj04XxQ/1k0 Kz1IOPvSXUkZglwC2G1jUm4ZoCnSLRsaJILf2m3bQKNjwG232CnBzrvEWF7asjGqojAq QCVuOu9fzIvcZIEz6YykfJT01UpjJyoxsdb147AVt80h715GIjpdQ8E5h07TCWLShcpg j1TmT8Ci8szYT21g3kNMT1N1A5APSPHXDzGLIacJH6Fl7R6eCvw05U/Le9xS3om4seHB MmiuoQSq73qDprXmAbhOzDKi9ENU+6l33KCsRBORoHu+hGw8/Fl/qeoCzhZRnHP9xkpP Q67Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=RL81rvvs/Gml0RB4nK/uZiakZMpnEEuvvcoEBU8Kgyk=; b=Nwpo/FLH2u1e1bmceXbulvS1We9iccZp+S0+QnA6obDGMJjvwPbWuyYyysUeBGHyE8 lC4DgAr4CX+wlWAPvC6WZXgi9dEWK8DhS6fPUJfATBG7hMGU925Z4EIArDU7nFcSSFFv ffbtOIL0mpkuRKhn9ooYgYHoMJKpfFWL4kocYndG5kmNwmoy74Tc+Mxuw2RIBf0LqS46 iNCDzR7oVUMhCrLow+UXv2X99Wv8GIiK+jxNC4t7+PYWhafN9mHNkWH/PhoiQ94ny4Ml a+Z8r8wiK3i2II5wm945YgMGCP2guk4T+26K3CoG35a4aLTLSQats+UD+xNdeeifKPoo RCVw== X-Gm-Message-State: AOPr4FXHBWC+Uu/3OUJoWCOoX1ByvMLZh4W09Z7NrMJA88Kxn3wiGMhglnOYitZJ/6F/Cg== X-Received: by 10.28.195.7 with SMTP id t7mr4046467wmf.96.1463150932264; Fri, 13 May 2016 07:48:52 -0700 (PDT) Received: from [192.168.0.98] ([93.188.182.58]) by smtp.gmail.com with ESMTPSA id jp2sm19012658wjc.16.2016.05.13.07.48.51 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 07:48:51 -0700 (PDT) To: =?UTF-8?Q?Fran=c3=a7ois_Laupretre?= , 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 15:47:16 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] [Discussion] Third-party editing of RFCs From: rowan.collins@gmail.com (Rowan Collins) On 13/05/2016 15:26, François Laupretre wrote [not in quite this order, I hope I haven't changed the meaning by grouping your sentences differently]: > 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. > > What does 'genuinely irrelevant' mean ? > Will you accept that someone deletes your comment because he finds it > 'genuinely irrelevant' ? Of course not. No, I think deleting points would be very rare, that's why I gave a strongly qualified definition of "genuinely irrelevant". You were the one that raised the notion of "irrelevant" comments, what definition did *you* have in mind? However, I *would* expect people to edit the wording of a point I added if it wasn't clear, or if it could be put more succinctly. > Maybe I am not candid enough but do you imagine what it could become on > a controversial RFC like STH ?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. Actually, given the volume of discussion on STH, I would have welcomed an attempt to summarise the main points that had been raised, because I simply didn't have time to read all the mails on the subject, and had to give up trying. And yes, such a summary would have been large (maybe in that case a sub-page would work better than a section, as Davey suggests), but think of it as proportional to the amount of mail discussion. If the archive of the mailing list threads covers 100 pages of A4, a summary covering one page of A4 is still an incredibly useful resource. I mentioned in a previous message encouraging links to list archives. In my mind, these sections should not attempt to *persuade* the reader, or to demonstrate the importance of a particular point, they should attempt to *inform* the reader that a point has been raised. > 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 makes it all too personal, in my opinion. As I said before, I think we need to encourage the view that RFCs are a collaborative process, not an adversarial one, and "I intend to vote against because of X" is very different from "I like this, but one downside I see is X". The points being discussed might be addressed in future edits of the main RFC text, or they might be tradeoffs that are need considering, but everybody voting decides are worth it on balance. Somebody might edit acting as "Devil's Advocate", summarising points they don't necessarily agree with, but have seen expressed. When somebody comes to vote, the "Discussion Summary" (possible better name for the section / sub-page?) would prompt them to consider the points that had been raised. Regards, Rowan Collins [IMSoP]