Some PEAR web-related proposals

Hi boys and (unfortunalty no) girls, I was a little bit away from my computer and has time to think about the PEAR future. The next proposals comes in my mind after reading about some german articles about OpenSource. 1. Add a feature request form on a prominent position on pearweb. A user on the german php newsgroup wrote, he reads the feature requests on the phpnuke website. Often the are written by users, not by programmers. The users have intresting ideas because they doesn't think about implemention. 2. Separate the PEAR bug tracking from the PHP bug tracking. All PEAR related stuff is at the moment only covered by one drop-down issue for pearweb, peardoc and all classes and extensions. Another problem is a user would markup a peardoc bug as documention bug, not as PEAR bug. 3. Add a News section equal to php.net. Nobody out there knows something about the PEAR installer, important releases and other new cool stuff. 4. Add a "Behind the scence" section maybe as an non standard part of the manual. This section should contain a regular summary of the PEAR-Dev mailinglist discussions (i have the weekly ZE2-ml summary in my mind). And this would be the right place for documentions about the internals of PEAR. I.e. a description of the internals of PEAR::DB or why IT doesn't work like xy. This could include subjective comments of the maintainer/programmer. This section is directed to PEAR developers not PEAR users. 5. Set up a Groupware. This means ToDo-Lists, Schedules, project list and a (human) ressource list. Why? Sometimes you have a request like: "I want to help, what could i do?". The answer would be "Here is your username and a passwort for your groupware. Check out your ToDo-list and add yourself to the human resource list". Schedules sounds awful for an opensource project, but i think we are professional enough to guess which time a project could need. So others could check the schedule and see "oh, Cox works on xyz since 2 months, although he only announced only 2 weeks, maybe he can help." The project list can help to avoid doing the same twice (like the HTTP_Client stuff at the moment). The human resource list should help to find developers which special experiences. I.e. Stig writes a database2mail class and need somebody who has experience with mail creation. So he type 'mail' into a form and get Richard as a specialist for the mail-rfcs. Or somebody has problems with the phpdoc comments... And we can build a PEAR developer community without giving everybody a CVS account to feel as a PEAR Developer. 6. Make more advertising! PEAR isn't brand into the mind of the PHP people. Maybe you remember the IRC discussion about PEAR banners with slogans like "Rasmus use PEAR, for what do you wait?". Why not create such banners? Some OpenSource-related sites offers free ads for non-commercial OS projects. Cu, Alex