Re: Quality control of PECL modules

From: Date: Thu, 23 Feb 2006 09:55:56 +0000
Subject: Re: Quality control of PECL modules
References: 1 2 3 4 5  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-3544@lists.php.net to get a copy of this message
That is going to end up being very subjective and it sounds time-consuming. It also seems a bit odd to ask extension authors to make a case for their contribution to some higher power. I'd rather try getting the authors themselves to objectively label their extensions appropriately. And like Sara mentioned, perhaps pull in some activity stats just to give people an impression about whether anything at all is happening with the extension. We could also let extension authors set some sort of "last tested with PHP v.X.Y.Z" thing and with each new version they could go and update that (without forcing them to create a new package hopefully) just so you get an idea that the maintainer is still around and is keeping an eye on new PHP releases. -Rasmus Andi Gutmans wrote:
I agree. I think we could even do some of these manually. Like we could decide what our guidelines for quality is, and then judge each extension individually. First time would be a lot of work, but after that, we could revisit only when the extension author asks for the change and provides adequate "evidence" for the extension to be upgrade.... Just a thought... I was merrily proposing to discuss how to resolve the issue. I think there are many ways to do it, and agree we should find a way which isn't too time intensive and preferably doesn't require lots of development. At 07:57 PM 2/22/2006, Wez Furlong wrote:
In General: These things sound really nice to have, but do raise the amount of development overhead; I'm not sure we have the resources to properly maintain them. Whatever we decide needs to be balanced against the amount of effort it takes to implement them.


« previous php.pecl.dev (#3544) next »