Re: Quality control of PECL modules

From: Date: Thu, 23 Feb 2006 06:53:40 +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-3540@lists.php.net to get a copy of this message
One of these attributes is "Interface Stability", which clearly defines levels of stability. We could adopt this nomenclature in our documentation and package releases.
This is another reason to be using package.xml 2.0 Ditto on this and the active maintainer flag.
Beyond that, we might want to take a page out of sourceforge's playbook and give some type of activity ranking to packages. Frequest pear install requests imply higher usage and therefor deeper testing (not a fair stat to bundled exts of course), and frequent cvs commit imply active maintenance. That's only half the picture of course as a package could be continuously building up feature bloat and none of those features actually work, but it's a component of the overall picture. It also seems like it'd be trivial to add the gcov score. In theory the more completely a package is tested the fewer bugs its likely to have. This one is unfair to the networking packages, but hey, you can't win all the time. I do like the idea of user ranking, but I think something like the manual's commenting system puts the power to rant (or rave) about a given package where it belongs; In the hands of the actual users. -Sara

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