Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103936
Message-ID: <1548953369.19409.21.camel@schlueters.de>
To: Zeev Suraski <zeev@php.net>, internals@lists.php.net
Date: Thu, 31 Jan 2019 17:49:29 +0100
In-Reply-To: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] RFC:  RFC Workflow & Voting (2019 update)
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Do, 2019-01-31 at 15:44 +0200, Zeev Suraski wrote:
> Without further ado, an RFC that’s attempting to comprehensively
> solve many of the issues that have plagued our RFC process since it
> was hastily introduced in 2011:
> 
> https://wiki.php.net/rfc/voting2019
> 

Being mostly outside I wonder a bit whether it would make sense that
inactive developers at some point lose their voting right.

Reasoning: If somebody is out of the project for 10 years they probably
lost track on how the language and needs evolved and just voting since
an old friend needed a deciding vote is bad. 

For groups like FIG I am uncertain. I think it is a good thing if we
push more things out of PHP itself into the userspace (JIT, FFI, ...
allow more and more stuff to be done in userspace) and thus
coordinating with userspace developers and setting standards and
interoperability there is good. However it are the maintainers who
(often voluntarily) have to maintain these things and overruling actual
maintainers is bad as they lose interest.

johannes