Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90813 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33835 invoked from network); 21 Jan 2016 22:49:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jan 2016 22:49:48 -0000 X-Host-Fingerprint: 77.179.13.15 x4db30d0f.dyn.telefonica.de Received: from [77.179.13.15] ([77.179.13.15:24524] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6B/14-09073-B8061A65 for ; Thu, 21 Jan 2016 17:49:48 -0500 Message-ID: <6B.14.09073.B8061A65@pb1.pair.com> To: internals@lists.php.net References: <59.F0.09073.49041A65@pb1.pair.com> Date: Thu, 21 Jan 2016 23:48:39 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Posted-By: 77.179.13.15 Subject: Re: [PHP-DEV] Handling of withdrawn RFCs From: flyingmana@googlemail.com (Flyingmana) On 01/21/2016 09:53 PM, Ronald Chmara wrote: > On Thu, Jan 21, 2016 at 12:33 PM, Flyingmana wrote: >> An RFC could still be valuable for the project, even if the original >> author leaved, so taking it over should be possible. And it should not >> be painful in any way. >> Would we need some rules in case multiple people want to take it over, >> or should we say the first one wins? >> Is there any way to abuse the taking over of an withdrawn RFC? > > Hypothetically: > > An RFC being used primarily for ongoing debate/argument/trolling > purposes could live indefinitely, generating hundreds, or thousands, > of messages, and changesets/PR's, and list churn, in the name of > "making sure an issue is adequately discussed and resolved". > > Even as individual trolls, marks, and sockpuppets were knocked down, > new ones could pick up the mantle of "but we're discussing important > things, here!", and continue the loop, only finally exhausting the > suite of RFC mechanisms all of the trolls/marks/puppets finally gave > up, or were someho0w being administratively prohibited from all future > participation. > > Which, if the PHP email lists were an endless trolling/argument/debate > forum like twitter or reddit, would be completely appropriate. > > This is all hypothetical, of course. > > -Ronabop > Thats a valid problem. How is this currently handled for the case, the troll is not willing to withdraw it? -Flyingmana