Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103968
To: internals@lists.php.net
References: <03f401d4b96b$18b9dc60$4a2d9520$@php.net>
 <1548953369.19409.21.camel@schlueters.de>
 <1fcbbaac-8edc-ad7c-92aa-2d21f6d0487b@gmail.com>
 <CAKOpQSxS2cqwwoEivPaxhVWuy_Z7FX4NZmPUkXXCz+xZ9jqY2A@mail.gmail.com>
Message-ID: <04dbc3fb-e4e5-51e9-4562-d29bcc49ef6d@lsces.co.uk>
Date: Fri, 1 Feb 2019 08:52:20 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <CAKOpQSxS2cqwwoEivPaxhVWuy_Z7FX4NZmPUkXXCz+xZ9jqY2A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: RFC Workflow & Voting (2019 update)
From: lester@lsces.co.uk (Lester Caine)

On 01/02/2019 08:34, Kris Craig wrote:
> The more I think about this, the less I like it.  According to the page
> linked to from the RFC, there are 51 current FIG members who would gain a
> vote.  So this RFC would strip most contributers of their voting rights
> (including me), while simultaneously adding 51 new voters, all from the
> same external organization (one that has been aggressively gunning for
> "official" recognition since its inception).  In other words, this RFC, in
> its current form, would have effectively handed control over the entire PHP
> project to FIG.  Though I'm sure it was never the intent, TBH, this does
> feel like a bit of a slap in the face to past contributors who still have
> good ideas to offer now and then and should still have a voice.

The question of the whether FIG is to become a core standard and 
everything is then based of it is perhaps the real RFC here? That move 
would bring FIG developers in simply because their contributions would 
be direct to the PHP code base? That it does now seem to be the de-facto 
standard may detract from a formal discussion as to if it should be THE 
roadmap moving forward? Much like composer is now so enshrined in new 
projects but is at adds with much legacy code? Bringing in blocks of 
'voters' who have a different development style before deciding if that 
style is acceptable just seems wrong?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - https://lsces.co.uk
EnquirySolve - https://enquirysolve.com/
Model Engineers Digital Workshop - https://medw.co.uk
Rainbow Digital Media - https://rainbowdigitalmedia.co.uk