Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Fri, 22 Jan 2016 10:23:10 +0000 (GMT)
To: Flyingmana <flyingmana@googlemail.com>
cc: internals@lists.php.net
In-Reply-To: <6B.14.09073.B8061A65@pb1.pair.com>
Message-ID: <alpine.DEB.2.20.1601221006000.3314@whisky.home.derickrethans.nl>
References: <59.F0.09073.49041A65@pb1.pair.com> <CAFWS2+Gk1uYSNEOCz7LzsQEMiLOokmGKix=b1pS5tuzhmwJQtw@mail.gmail.com> <6B.14.09073.B8061A65@pb1.pair.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Subject: Re: [PHP-DEV] Handling of withdrawn RFCs
From: derick@php.net (Derick Rethans)

On Thu, 21 Jan 2016, Flyingmana wrote:

> On 01/21/2016 09:53 PM, Ronald Chmara wrote:
> 
> > 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.
> 
> Thats a valid problem.
> How is this currently handled for the case, the troll is not willing to
> withdraw it?

It isn't *really*. Which is what I hopefully think the current process 
of establishing our values, guidelines, a CoC and a Mediation Team should 
address.

And in an extreme case, with continuous trolling, a "resolution" (RFC 
like thing) could be put up for vote with the rest of internals to ban 
these people from the project. This is only mostly hypothetical, as it 
has happened once in the ~15 years I've been involved, although we 
didn't go through a process then. And I sincerely hope that was the last 
one too. 

cheers,
Derick