Re: Move internals discussion to a better medium
| From: | Marcio Almada | Date: | Sun, 02 Aug 2015 20:19:12 +0000 |
| Subject: | Re: Move internals discussion to a better medium | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-87537@lists.php.net to get a copy of this message | ||
Hi
2015-08-02 16:52 GMT-03:00 Rowan Collins <rowan.collins@gmail.com>:
> On 02/08/2015 20:10, Marcio Almada wrote:
>>
>> As you pointed github issues, it's worth noting that Rust internals
>> already use github to manage RFCs:
>>
>> https://github.com/rust-lang/rfcs/pulls?q=is%3Aopen+is%3Apr+label%3AT-lang
>
>
> That's interesting. Do you have a link to any documentation on the process
> they use?
You can see the process outlined here
https://github.com/rust-lang/rfcs#what-the-process-is.
> For instance, how does the RFC gain final approval / rejection?
The biggest difference regarding "approval" is that we express
"consensus" by having a vote with 2/3 majority (voting makes sense
here because consensus by discussion rarely happens anyway).
On their side, they usually don't have a voting phase like we do, the
"consensus" is built rationally during the discussion phases. See the
list of RFCs in final phase
https://github.com/rust-lang/rfcs/pulls?q=is%3Aopen+is%3Apr+label%3Afinal-comment-period,
as an example.
Marcio