Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90806
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.53 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <59.F0.09073.49041A65@pb1.pair.com>
References: <59.F0.09073.49041A65@pb1.pair.com>
Date: Thu, 21 Jan 2016 12:53:20 -0800
Message-ID: <CAFWS2+Gk1uYSNEOCz7LzsQEMiLOokmGKix=b1pS5tuzhmwJQtw@mail.gmail.com>
To: Flyingmana <flyingmana@googlemail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Handling of withdrawn RFCs
From: ronabop@gmail.com (Ronald Chmara)

On Thu, Jan 21, 2016 at 12:33 PM, Flyingmana <flyingmana@googlemail.com> 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