Re: Pear web wishlist

On Sun, 2002-01-27 at 21:37, Björn Schotte wrote: > First of all, great work on the web page! > > > * release-upload.php > > Automatic email the full anounce of the new release to pear-general (and > > pear-dev?). > > This is a good point, but imagine having 50.000 PEAR > classes in the future. This would cause much mail > traffic IMHO although releases wouldn't be every day. pear-announce@lists.php.net strikes me as the obvious solution to this. > Some thoughts and comments (may be already planned, > I didn't follow every thread on this list): > > - account-info.php: replace [Edit] text link with the > small edit image. (I know it's cosmetics and should > be low priority) > > - http://pear.php.net/manual/en/: what are the plans > here? Having a single documentation for all 50.000 > PEAR classes? Or having both, single documentation > and each PEAR class having its own doc? Right now there's a massive effort in just documenting stuff. The result is monolithic, but documentation should be part of each release at some point. We need to figure out how to do this in practice though. > - package-info.php: HTML table "Package dependencies" > is wider than the other tables. > > - package-info.php: "License" should be linked to the > appropriate license URL, if available We should probably add the full text of each license somewhere, and link to that. > - packages.php: enable browse by name, not only by > category. You mean just a straight sort by name? > - packages.php: ">>" should be linked to the top category. It's supposed to be a "more from this cateogry" link. Could be more intuitive. > - packages.php: what about displaying if there have been > releases for a specific package? Kinda like an activity indicator? > - general package statistics: how much releases total, > how much stable/alpha/beta releases Good idea. - Stig