Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107465
MIME-Version: 1.0
References: <67911D3D-CBC1-4847-9F4B-3C895EF84741@newclarity.net> <4ed1fb31-a8e4-bff7-54f5-c66c95c692c4@alec.pl>
In-Reply-To: <4ed1fb31-a8e4-bff7-54f5-c66c95c692c4@alec.pl>
Date: Thu, 10 Oct 2019 09:30:40 +0200
Message-ID: <CAG9XoMTU+X1zTjdZekjHE6b0nDnckxryLKhbNumWa_d45B6tqw@mail.gmail.com>
To: "A.L.E.C" <alec@alec.pl>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009fa065059489616a"
Subject: Re: [PHP-DEV] Constraints and userland@
From: benjamin.morel@gmail.com (Benjamin Morel)

--0000000000009fa065059489616a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> 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 do like the idea very much as well. However, if this is to be automated,
I wouldn't base the right to vote on the number of commits, but rather on
the number of GitHub stars, as it's way too easy to create artificial
commits on a new account at any time.
For example, allow any repository owner or main committer (for orgs) for a
repo with >=3D 100 stars.

Or, avoid doing anything automatically, just decide on a baseline set of
requirements that can be verified automatically (like at least n commits to
public repos, or at least one public git repo with >=3D n stars, etc.) then
review each *passing* application manually. This way the number of
applications should be manageable, there could be a queue that all current
maintainers could have access to and take a few minutes here and there to
review.

By keeping the review process manual, we can also easily revoke someone's
voting rights if the application turned out to be fraudulent (accepted by
mistake).

=E2=80=94 Benjamin

--0000000000009fa065059489616a--