Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104304
To: "'PHP internals'" <internals@lists.php.net>
References: <CAOwTYAsitSY24sq++t_Owfmmg7ck7Z+5HbwOAkHpKs1Mh5wfQA@mail.gmail.com>
In-Reply-To: <CAOwTYAsitSY24sq++t_Owfmmg7ck7Z+5HbwOAkHpKs1Mh5wfQA@mail.gmail.com>
Date: Fri, 8 Feb 2019 12:51:02 +0200
Message-ID: <0ea201d4bf9c$30103940$9030abc0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: he
Thread-Index: AQIvs8RV5aD2XOmnw2NlFDlZ7c91LaUfz7Hw
Subject: RE: [PHP-DEV] VOTE abolish narrow margins
From: vsuraski@gmail.com ("Zeev Suraski")



> -----Original Message-----
> From: Joe Watkins <krakjoe@php.net>
> Sent: Friday, February 8, 2019 10:51 AM
> To: PHP internals <internals@lists.php.net>
> Subject: [PHP-DEV] VOTE abolish narrow margins
>=20
> Morning all,
>=20
> As promised, abolish narrow margins is now open for voting:
>=20
> https://wiki.php.net/rfc/abolish-narrow-margins

Reasons I voted 'no':

- This is clearly rushed.  A more comprehensive RFC is in the works and =
already under discussion.
- Substantial changes were made last minute, without allowing reasonable =
time to discuss, or for people to even acquaint themselves with the =
changes.  As an RFC that deals with process, that's an extremely bad =
precedent.
- It places strong bias for status quo even in cases where one does not =
exist.
- It does not tackle the voting eligibility issues we have.

The general idea is good, the implementation & surrounding process are =
bad.

Zeev