Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87537
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <55BE74F1.3030006@gmail.com>
References: <CAGbiJu-No6nmVt6O05e6oiEJ1jBD-T2fXxLJSMpksf2CE_9HJw@mail.gmail.com>
 <CAOsHV+v7Rwg=DEhtpqc3XzwDqw1Q7aX3_Mvu8FUZhVLeM77jHA@mail.gmail.com>
 <CAGbiJu9_10HU2xCr=rUp72hxPgyvXxVf42s67W_4WorNCANpLA@mail.gmail.com> <55BE74F1.3030006@gmail.com>
Date: Sun, 2 Aug 2015 17:19:12 -0300
Message-ID: <CAOsHV+ufQv+8BUhoRBD2ihoOaF3mZ0F2nLfBogxa1AV9=HGhYQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Move internals discussion to a better medium
From: marcio.web2@gmail.com (Marcio Almada)

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