Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90822
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.173 as permitted sender)
To: Flyingmana <flyingmana@googlemail.com>, internals@lists.php.net
References: <59.F0.09073.49041A65@pb1.pair.com>
Message-ID: <56A1CEC3.4090808@gmail.com>
Date: Thu, 21 Jan 2016 22:40:03 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <59.F0.09073.49041A65@pb1.pair.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Handling of withdrawn RFCs
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> The Goal is, to not have this argument again against someone taking over
> a withdrawn RFC. Means this should end in some rules/guidelines
> regarding RFCs. (Advice what would be needed, like for example an RFC,
> is very welcome)

I think if someone is going to abandon an RFC, it would be a good
practice to ask first if somebody wants to take over. If yes, then
nothing happens. If not asked or asked and nobody responded immediately
but then picks up later, it should be as if RFC work is continuing.
Since vote didn't happen, no reason to treat is as failed.

Yes, people could probably play games with it. But so far we didn't see
it, even if we have a bit of drama, everybody is acting in a good faith
- i.e. if somebody withdraws RFC, it's because they don't want/can't
work on it anymore, and if somebody picks it up, it's that because they
are interested in the same thing.
If that changed, we can deal with it then.

-- 
Stas Malyshev
smalyshev@gmail.com