> After having requested a PECL account[1], you will have to remind the > PECL admins by writing to this mailing list in regular intervals (say, > once per week) that they either approve or reject the account. > > [1] <https://pecl.php.net/account-request.php>
The alarm and snooze buttons once per week are quite normal in many of the open source projects I think. There is an issue (and also challenge) with PECL, the way I got to know the processes here a bit. Having an account and extension for idling doesn't help anyone. Yet, also current maintainers and Git managers can't tell in the beginning if the account will be possibly the next major core extension maintainer and contributor that will improve PHP in enormous ways. Imho, PECL should ultimately go in the direction of "unmoderated" registration a bit and allow any extension to be registered there. But to get to there is a very long way actually with adjusting the apps and command line pecl tool. That way, new users could create their wanted extensions without issues of being in naming conflict with one another (by using vendor prefixed namespaces) and registration via additional Git(Hub) or other authentication service or standalone registration where no approval is required. So, at this time, yes, the best way is probably to create a useful extension. All the formalities are kind of logical and self-evident on its way with having a good extension. Or start simpler - by sending patches to existing extensions. There are quite a lot of bugs opened at some... -- Peter Kokot -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
