Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103930
MIME-Version: 1.0
References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net> <CAJW__o1q3e1+1DoFVE3dpUdn=f-AnPHuVXpM+6jruQYYrJ6PSQ@mail.gmail.com>
 <CAKOpQSzQiEp7G9uvEYq_RnUFyy0bDaOZ8qBqR1OiAGTcQ-TXOA@mail.gmail.com>
In-Reply-To: <CAKOpQSzQiEp7G9uvEYq_RnUFyy0bDaOZ8qBqR1OiAGTcQ-TXOA@mail.gmail.com>
Date: Thu, 31 Jan 2019 18:10:31 +0200
Message-ID: <CAJW__o3EnWt3xePJZOBzXuj=M2USi-xGY+Y-fWWODRBc-bpCRQ@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: Zeev Suraski <zeev@php.net>, PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: RFC Workflow & Voting (2019 update)
From: kalle@php.net (Kalle Sommer Nielsen)

Hi Kris

Den tor. 31. jan. 2019 kl. 18.03 skrev Kris Craig <kris.craig@gmail.com>:
> Given how complex and controversial this question of restricting who can =
vote is, I propose that it be moved to its own RFC instead of being bundled=
 with this one.  It would certainly boost likelihood of passage, if nothing=
 else, as there are a lot of good ideas in this RFC.

While that makes sense, I do believe it should be sorted at the same
time. This can be solved by secondary votes on how to approach it
within the RFC.


--=20
regards,

Kalle Sommer Nielsen
kalle@php.net