Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103996
MIME-Version: 1.0
References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
In-Reply-To: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
Date: Fri, 1 Feb 2019 17:13:46 +0000
Message-ID: <CA+kxMuTpM=kfLFUtxRY57eWT3N6jx2A9m7MumbSDj=OPuXcdAA@mail.gmail.com>
To: Zeev Suraski <zeev@php.net>
Cc: PHP internals <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: Danack@basereality.com (Dan Ackroyd)

On Thu, 31 Jan 2019 at 13:44, Zeev Suraski <zeev@php.net> wrote:
>
> Without further ado, an RFC that=E2=80=99s attempting to comprehensively =
solve many of the issues that have plagued our RFC process since it was has=
tily introduced in 2011:

Hi Zeev,

Please can you very clearly state what problem you are trying to solve
by changing the rules about who can vote.

Without presenting the problem, and why your solution is the correct
one, it's not obvious that the change being proposed is either needed
or the right one choice.

Additionally, giving a vote to members of PHP-Fig is not a good idea
for multiple reasons.

* They are not language designers and they do not know PHP internals.
They cannot evaluate the tradeoffs of changes.
* The membership requirements of the FIG were 'gamed' by some projects
by using bots to create fake stars on Github and number of downloads
to meet the requirements for FIG membership.
* Other members such as Symfony, Laravel and Doctine have left FIG.

btw, you seem to have completely overlooked extension maintainers from
your list of people who should have a vote on PHP internals.

cheers
Dan
Ack