Having stuff pushed onto the dev list / making the QA side of it a bit
more
open would be awesome - failing that, an easy to find link to the QA bug
summary from the pearweb site would do the trick.
It's not closed...just join the pear-qa list. We try to keep things on
separate lists to let people only get what they want to get.
Not to nit pick, but I'd never guess that the first place to "get involved
with pear" lived at
http://pear.php.net/qa/ - even when I followed the link
just then, and read everything on the page, it doesn't sound like the right
place to go.
In terms of the bug summary, the easiest way to find this is to browse to
http://pear.php.net/bugs/stats.php
http://pear.php.net/bugs/stats.php is great from a 'overall look at pear'
point of view, but kind of overwhelming for a 'I just want something to
fix'... where as the summary information pushed out in the qa lists stuff is
just what I'm looking for...
ID Status Summary (900 total)
===============================================[Archive_Tar]==================
4013 Open Ignoring files and directories on creating an archive..
9520 Open Doesn't allow in-memory manipulation of tar files.
10145 Open Patch to return a Pear Error Object on failure.
Package name + one line of what it is to get me curious... add a link to the
id... voila! I can find something worth doing.
--
Browser feels a little bit slow? http://thebetterbrowser.com/newer