Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107464
To: internals@lists.php.net
References: <67911D3D-CBC1-4847-9F4B-3C895EF84741@newclarity.net>
Openpgp: preference=signencrypt
Message-ID: <4ed1fb31-a8e4-bff7-54f5-c66c95c692c4@alec.pl>
Date: Thu, 10 Oct 2019 07:46:03 +0200
MIME-Version: 1.0
In-Reply-To: <67911D3D-CBC1-4847-9F4B-3C895EF84741@newclarity.net>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Constraints and userland@
From: alec@alec.pl ("A.L.E.C")

On 10/9/19 11:16 PM, Mike Schinkel wrote:
> As a straw man proposal there could be a set number of seats (~250?), divided up by how they are involved in PHP; corp developer, independent developer, framework vendor, hosting company, etc. They should participate as representatives of userland rather than as representatives of their own opinions. They would get to vote on things so we could gauge userland's interests, but their vote could only be used to veto an accepted RFC, and internals@ could override the veto if, say, 90% of internals@ members voted to do so.  

As a part of PHP community I like the idea. I'd propose something that could make the
proposal simpler in implementation.

Create a poll system where users are authorized to be registered and be able to vote if
they are github/gitlab users with >1000 commits in projects where PHP is one of the main
languages. I think something like that should be doable and will not require any "paper
work". It should give quite good estimation on the community preferences (even if it would
exclude non-open source entities).

I very much like the idea such vote would be a veto which would rise the bar for an RFC to
pass.

ps. first time poster, but I couldn't sit quiet seeing what's going on on the list recently.

-- 
Aleksander 'A.L.E.C' Machniak
Kolab Groupware Developer         [http://kolab.org]
Roundcube Webmail Developer   [http://roundcube.net]
----------------------------------------------------
PGP: 19359DC1 # Blog: https://kolabian.wordpress.com