There seems to be some different point of views how to handle withdrawn RFCs. As this is a separate point and maybe a more complex point I want to start this as an additional Thread here.
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) As already was noted by someone else, seeing an RFC as failed if it gets withdrawn has some serious downsides and potential to get abused. Most obvious the possibility to kill RFCs by increased pressure against the author. I think that deserves to get targeted, as leading an RFC which gets some greater public attention creates in itself already some pressure, not everyone is able to endure. 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? best Regards, Flyingmana -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
