PEAR developers guide

Hi, I will soon start writing the PEAR developers guide and I would like to hear some feedback concerning my ideas. Right now I thought of the following contents: ==================================================================== * What PEAR means for a developer * High quality code * Chance to release his/her own code and become famous * Contributing own code * Requirements for contributing code * Conforming to the coding standards * Documentation in an appropriate format (plain text, docbook) * The contributor is willing to provide support for his package(s) and is willing to release future (bug-fixing) versions. * How to contribute code * CVS account, pear.php.net account * Finding an appropriate package name * Bundling releases * How to support the PEAR community * Reporting and fixing bugs * Buying things from wishlists :) * Contributing new features to packages * Becoming the new maintainer for an unmaintained package ==================================================================== Right now this is work in progress and if you have topics that should be additionally mentioned, post them now or be quiet forever :-). - Martin -- Martin Jansen, <mail@martin-jansen.de> http://www.martin-jansen.de/