On Tue Oct 01, 2002 at 06:3320PM +0200, Lukas Smith wrote: > Mainly there are still too many questions marks regarding stuff like: > - How are packages maintained (especially when the leading developer is > gone ... PEAR DB currently seems to be an example of this with bugs > hanging in the air and nobody feeling responsible)
I guess sending patches to pear-dev should be the best way. > - How are packages proposed and when are they accepted http://pear.php.net/manual/en/developers.contributing.howto.php > - And when they are accepted how makes sure that the person gets the > necessary access The PEAR administrators take care of the PEAR website accounts and the PHP Group does the same for CVS accounts. > - A Guide to lessen the endless naming debates. http://pear.php.net/manual/ > - Should packages be pearified before getting into pear cvs or is > afterwards ok? Is there even a general rule? http://pear.php.net/manual/en/developers.contributing.php. > - Where is a tutorial explaing all of the answers to above questions? Most of the stuff is explained in the PEAR developers guide: http://pear.php.net/manual/en/guide-developers.php > The results of this would need to put into action. Therefore I think > that PEAR will not be ready until the end of december. I think PEAR is pretty fare and it is absolutely read for a first appearance on the official stage. -- - Martin Martin Jansen http://martinjansen.com/ -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
