priorities for PEAR project as a whole

Hello all, I want to re-iterate the priorities for PEAR as a project that I brought up last spring, and see if we might be able to pull a few of you off of other projects for a short while to expedite this process. Summary: #1: make the PEAR website PEAR-installable, instead of syncing from CVS #2: add package groups for the website and for installer REST #3: any other changes, political or technical Long version: What problems do we have in PEAR at the moment? First, there is an awful lot of bickering over how we're going to do the PHP5 thing in PEAR. Second, almost all recent political decisions have not been clearly documented on the website. Third, we have lots of packages and very little oversight and cooperation between developers to do QA and assist each other with details. Most of these problems go back to the website, and the way that it directs the political and technical discourse in PEAR. Right now, it is hard - and also dangerous - to update the website, because it is synchronized directly from CVS. Hence, priority #1: #1: make the PEAR website PEAR-installable, instead of syncing from CVS. This will allow us to try out some experimental things, and also make it much easier to QA the website prior to a public release, spurring innovation and stability. Part of that innovation involves a technical change to the website that will enable a better political dialogue in PEAR: #2: add package groups for the website and for installer REST this will allow us to do a lot, especially with separating older packages from newer, and even grouping related packages in intuitive ways beyond static categories. #3: anything else deciding on the exceptions usage, re-organizing PEAR group - all of this can wait until we have a more dynamic front page and presence. Comments? Thanks, Greg