Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104107
To: internals@lists.php.net
References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
Message-ID: <a7317417-c810-8076-724b-a1c8750a8d13@hoa-project.net>
Date: Mon, 4 Feb 2019 10:51:00 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0)
 Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
Content-Type: multipart/alternative;
 boundary="------------1306CA4CF6ACEA998A0B9BCD"
Content-Language: en-US
Subject: Re: [PHP-DEV] RFC: RFC Workflow & Voting (2019 update)
From: ivan.enderlin@hoa-project.net (Ivan Enderlin)

--------------1306CA4CF6ACEA998A0B9BCD
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello and thanks for the RFC.

I think the Eligible Voters Section is too complex to be 
addressed/bundled in this RFC. I think it deserves another RFC.

Most discussions here are rightfully about this section. To add my opinion:

  * I don't understand the special treatment for PHP-FIG. This group
    first intent was to reflect the “major implementors point of view”
    in order to make common agreements/standards about some practises.
    Based on that, yes it makes sense to include PHP-FIG into the
    Eligible Voters group. However, some projects have decided to step
    away from PHP-FIG for various reasons I won't list here (I can
    mention sabre.io or hoa-project.net because I was/am involved in
    those projects). Thus, they are excluding themselves from the
    Eligible Voters group? It doesn't make sense, and it does not sound
    very democratic :-).
  * Some people don't contribute to the php-src repository (like
    myself), but create extensions, participate to the ecosystem, or
    push PHP further. As an example not related to myself, I think of
    PHPStan or Doctrine, both projects are important PHP projects, with
    an extreme usage of PHP features as a language, and their authors
    are in a good position to give feedbacks on PHP RFC, or to write
    ones. The metrics that are currently listed in the RFC to be an
    Eligible Voter entirely exclude this population. If this population
    is excluded, I'm afraid that the PHP future will defer from the real
    usages/expectations of the language.
  * I don't understand why keeping existing voters is an issue, it's not
    motivated, and consequently I can only disagree with the
    grandfathering section.

The rest of the RFC is very interesting. It would be sad to miss it 
because of the Eligible Voters Section. I suggest to split it into 2 RFC.

Regards.

On 31.01.19 14:44, 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
>
>   
>
> Emphasis on ‘attempting’.  I’m sure there are still a lot of holes in it that should be plugged before we vote on it, but instead of waiting indefinitely – I’d like us to start discussing it.
>
>   
>
> Comments and suggestions welcome.
>
>   
>
> Zeev
>
>   
>
>   
>
>

--------------1306CA4CF6ACEA998A0B9BCD--