Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107129
To: Dan Ackroyd <Danack@basereality.com>,
 PHP internals <internals@lists.php.net>
References: <CA+kxMuTvOjnV18LwVP=n_JXwm66932uGV-m9zRSsFgiX9Jcy7g@mail.gmail.com>
Message-ID: <7e5814f6-7b6e-d331-c065-7e06eb21d0c8@cubiclesoft.com>
Date: Sun, 15 Sep 2019 17:05:16 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120327
 Thunderbird/11.0.1
MIME-Version: 1.0
In-Reply-To: <CA+kxMuTvOjnV18LwVP=n_JXwm66932uGV-m9zRSsFgiX9Jcy7g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Changing PECL signup flow.
From: thruska@cubiclesoft.com (Thomas Hruska)

On 9/15/2019 10:11 AM, Dan Ackroyd wrote:
> HI internals,
> 
> Currently, it is quite difficult to signup to get a PECL account.
> 
> We have a somewhat deliberately obtuse form to signup through, which
> then needs to be manually approved by someone with the appropriate
> karma.
> 
> Over the past year two people who I know from the community have
> reached out to me to ask "we've submitted our account application, how
> do we get approved now", after their application has sat un-actioned
> for weeks. And only after I spoke to someone with the appropriate
> karma was their account approved.
> 
> I would like to suggest the following changes both to allow it easier
> to publish PECL extensions, and also prevent that causing problems.
> 
> # Allow a new signup method
> 
> Allow people who want a PECL account to submit a link to github repo
> (or alternative VCS provider) that contains a 'ready-to-ship' PHP
> extension repo.
> 
> We (or probably, I) will provide a tool that allows people to check
> that their repo is ready to be submitted to PECL, including all the
> appropriate things like buildconf works, the name of the project is
> set in the appropriate place.
> 
> On signup, when someone submits a 'ready-to-ship' extension we will
> have code that checks the extension for conformance, and if the
> extension looks ready to go, their application is listed on a page
> where anyone with PECL karma can approve or reject the application.
> 
> This would remove the bottleneck of only a few people being able to
> approve the PECL accounts, while still blocking most inappropriate
> signup attempts.
> 
> # Change voting rights
> 
> Getting a pecl account would explicitly no longer give or require a
> php.net account, and wouldn't confer voting karma. To be clear, I am
> actually unsure whether it's intended for people with PECL accounts
> should get voting karma; I know some people did but apparently not all
> have.
> 
> Although giving those a php.net account and voting karma is
> appropriate for extensions that are widely used, it is not appropriate
> for extensions that belong to a company and don't represent a wider
> community interest to automatically get a php.net account and/or
> voting rights.
> 
> For example, there are multiple extensions that allow Application
> Performance Monitoring. Those extensions are not 'owned' by the
> community, but instead represent a commercial interest.
> 
> Those two changes should allow extensions to be listed on PECL much
> more easily, without being too disruptive to the PECL site.
> 
> Thoughts?

Sounds good to me.

I thought the php.net account was for incorporating new documentation?

-- 
Thomas Hruska
CubicleSoft President

I've got great, time saving software that you will find useful.

http://cubiclesoft.com/

And once you find my software useful:

http://cubiclesoft.com/donate/