Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115523
MIME-Version: 1.0
In-Reply-To: <7d912ba3-c00c-cf5f-24f7-8e9ec371b2cc@alec.pl>
References: <96487D08-8573-4308-A11C-3118113C03DA@gmail.com>
 <CAF+90c_Bm5J7-CxpidME89iMATqryRH2Mc0mTog_KAUJccuw5w@mail.gmail.com>
 <CAAKU0ukYZUU5UO1VPsdbrjN16JnKp563aecrx3_O+n-eQmzDjg@mail.gmail.com>
 <9d55f768-41d2-d970-8417-aa786d86b984@heigl.org> <b550a7ec-901a-ab9b-59f8-14afefa91c21@heigl.org>
 <7d912ba3-c00c-cf5f-24f7-8e9ec371b2cc@alec.pl>
Date: Tue, 20 Jul 2021 16:12:21 +0500
Message-ID: <CAC_PL4yhgAiu5MULXQr0zAgsQdhXQHSuNeiP=Y2xuQ5L0YpSCw@mail.gmail.com>
To: Aleksander Machniak <alec@alec.pl>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Request for karma to vote on RFCs
From: office.hamzaahmad@gmail.com (Hamza Ahmad)

I am not going to critique the RFC; rather, I say that this RFC needs
a fresh rewrite because I find more like it a set of instructions. The
proposal needs to be a detailed one. It seams as if it is written
hastily.

As Tobias has mentioned that he has been reading the RFCs for years,
there is a large number of people that do the same. After this
discussion has been started, people are closely observing the dialog
and waiting for their chance to become a voter.

Thus, there needs a clear framework that will lay a foundation for the
future of PHP. There are a lot of voters out there, but you will
hardly see 60 or 70 voters participating in the process. There needs
to be a system that provides others obtain the right to vote and
contribute to the language. Here, Tobias is not a single instance. I
honor him and also respect the other community members that want to
vote for the features. Many feature requests were declined just
because 25 to 30 people had disliked them.

Meanwhile, nobody wants a rush. Thus, the policy should be flexible
enough that it incorporates the great talent. It should not be that
strict that nobody ever tries to partake in the process, nor that
flexible that somebody establishes its feed and one day hack the
source. We have seen how hackers tried to use Nikita's name for their
own purpose. Why cannot a hackers group try to join the team?

To avoid such incidents. One should not get merging rights after
getting voting rites. Rather, it should be a separate process. Also,
it should be cleared, so the language development is successfully
passed on to the next gen. I have another idea that can initially
allow Tobias and other community members participate in the process.
What about 80 20 system? 80 percent vote will come from the current
voters and 20 percent from the community.

Best

Hamza

On 7/20/21, Aleksander Machniak <alec@alec.pl> wrote:
> On 20.07.2021 08:22, Andreas Heigl wrote:
>
>> the requester has contributed to the PHP sourcecode ecosystem. That
> can be (but is not limited to):
>>    Contributions to the PHP-Sources
>>    Contributions to the Documentation or the Translation
>>    Triage, solve or otherwise interact with bugs
>
> Voter would need an easy way to verify that information. Otherwise we'll
> be facing "-1, because I can't verify or have no time to do it" votes.
>
>>    Help in the maintenance of the PHP Infrastructure
>
> This has nothing to do with PHP language, and it cannot be verified by
> anyone. I suggest to remove this point.
>
> I think the voting would need to be in a form we're using for RFCs,
> counting votes on mailing list will be error-prone and time-consuming
> (you don't know who's a voter).
>
> --
> Aleksander Machniak
> Kolab Groupware Developer        [https://kolab.org]
> Roundcube Webmail Developer  [https://roundcube.net]
> ----------------------------------------------------
> PGP: 19359DC1 # Blog: https://kolabian.wordpress.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
>