changes to "RFC::Proposed PEARWEB Changes"

full doc here... <http://pear.php.net/pepr/pepr-proposal-show.php?id=448> the changes are roughly... ------------------------------------------------- #6 moved to IN PROGRESS, and comments added about Arnaud's change: 6. view of all unmaintained packages... [Amir Mohammad Saied] It's impossible to browse all of them to find out which one(s) is marked unmaintained, and I can't find any way to find unmaintained ones through the web-interface. [Craig Constantine] Turns our there is such a page, but requires pear.qa karma. Clean this page up and make it visible to a larger audience. Not necessarily the endusers, but at perhaps as wed as "everyone with pearweb account." [Arnaud Limbourg] 2-oct made changes [Craig Constantine] We need to link this from somewhere. pearweb side bar is already very busy. How about a section on the QA page? IFF pear.dev karma, THEN a "Related tools" heading and a "list packages with no maintainer" link to: /qa/packages_orphan.php ------------------------------------------------- #2 moved to a new #8. (We now have several docu related ideas.) -------------------------------------------- #5 has become: 5. improvements to enduser navigation/use... [Christian Weiske] When seeing the PEAR homepage the first time, you probably don't go through the list at the left side or read the text fully. Most attention is drawn to the links at the bottom: "Developers - Upload and New Package" and "PEPr - Browse and New Package" In my opinion, directly above these should be: "Users -Browse packages and -Search packages". This would make it more convenient for not-so-regular-or-new users to find packages faster. --------------------------------------------- The following are all new (to the document): 8. improvements to enduser documentation... [multiple people] Permit enduser comments to documentation ala PHP's comments posted by endusers [Dan Scott] Streamlining the Web site to better integrate packages and their corresponding documentation? It's not clear to me why a user that wants API documentation generated from phpdoc comments needs to search or browse through the package list of the PEAR web site, rather than finding a link that is automatically generated in the corresponding section of the PEAR manual. This effectively forces users through a navigational maze. [Christophe Gesche] As a package can have many stable release but only one end-user doc per package. Proposal: In end-user doc. each page would indicate from/to package version concerned by the current page. Like it's done for each function on php Documentation. 9. package statistics... [Joshua Eichorn] I'd like too see some sort of statistics return. I don't care so much about fancy graphs etc, but it would really be nice to at least have a lifetime and current month download # available right from the main package page. [Mika Tuupola] They could be even generated once a day via cronjob. No need for live updating. 10. package information page... [Arnaud Limbourg] Have a way of indicating previous maintainers as Emeritus or something like that rather than "inactive".