Re: RFC: RFC Workflow & Voting (2019 update)

From: Date: Tue, 05 Feb 2019 10:09:36 +0000
Subject: Re: RFC: RFC Workflow & Voting (2019 update)
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to internals+get-104170@lists.php.net to get a copy of this message
Hi again, On Tue, Feb 5, 2019 at 10:37 AM Zeev Suraski <zeev@php.net> wrote: > > Regardless of what you did, actually obtaining full voting rights > meant you had to ask for a VCS account, and have a reasonably good > explanation on why you need one - enough to convince one of the folks > with admin rights on master.php.net to click the 'Accept' button. This is what I don't understand. On one hand you say one needs to make a convincing enough request, so that it may be granted by admins such as yourself. To me, that sounds reasonable-ish (with some reserves, but certainly different to yours) as I can't imagine that commit access to a project like PHP is handed out left and right to anybody who wants it. But in the same breath you also say that's a low bar. If that's a low bar (to which I don't agree, but I also don't make these decisions so idk), then perhaps the vetting process itself should be revised. How can you trust your peers to grant commit access, but not a say in how things should go forward? That's a contradiction to me. > That's all. Immediately, one has identical rights to someone who may > have been spending years of their time on PHP, in a one way ticket. > There will always be new kids in the block and you have to accept that if you want to attract any contributors at all. Cheers, Andrey.

« previous php.internals (#104170) next »