mission statement thoughts for PEAR

Hi all, Don't forget to post your thoughts on the most important aspects of PEAR's mission. Here are mine (some are duplicates of thoughts by others). I've split them into missions from the user's perspective, and from the developer's perspective. Users: PEAR should be a repository of high-quality, well-documented code. PEAR should provide self-contained libraries that can be used to implement solutions not already built into PHP - PEAR should extend PHP, not duplicate it PEAR should provide PHP-only alternatives to non-standard extensions PEAR should provide full-scale applications to handle infrastructure-related PHP needs (phpdocumentor, etc.) PEAR should require a high barrier to the "stable" label, requiring full docs, full unit tests, and API review PEAR should have an easy-to-understand and community-based review system of all packages PEAR should seek to support PHP development in general by concentrating on interoperating with other solutions out there, such as eZ Components, Zend Framework, Cake, Symfony, Solar - to make it as easy as possible for users to switch and to coordinate libraries from different sources. Developers: PEAR should be a hotbed of innovation as well as a source of stable code, supporting and rewarding active developers with fame and space to host and to advertise their code. PEAR should encourage cooperation between developers to provide simple, unified API coordination so it is easy to plug in any PEAR library. PEAR should provide an "alphaworks" where there are looser restrictions on entry PEAR should provide mini-communities within PEAR organized around like packages (all HTML processing packages, all PEAR installer infrastructure packages) where developers can coordinate better, and support this within the pear.php.net website. Greg