Hi, Le 21/01/2016 21:33, Flyingmana a écrit :
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.
>...
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?
IMO, a withdrawn RFC should not be considered as failed and, unless it contains a more precise status ('suspended until ...', 'waiting for ...'), it can be taken over by anybody. It is fair to ask the original author's permission but not sure this must be required.
I would propose a minimal period between withdrawal and takeover (48 hours, 72 hours ?). This could prevent lightning-fast takeover to be used as a political trick. During this period, people could volunteer for taking over the RFC but the RFC itself would be frozen.
If multiple people want to take over, and if they cannot agree on co-authoring, the only fair solution is probably to create concurrent follow-up RFCs. The STH case shows that it should be avoided as much as possible but I'm still looking for a better solution.
Regards François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
