Re: future of PEAR (was [PEAR-DEV] [Call For Votes] PHP::Fork)
| From: | Björn Schotte | Date: | Tue, 11 Nov 2003 07:00:00 +0000 |
| Subject: | Re: future of PEAR (was [PEAR-DEV] [Call For Votes] PHP::Fork) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23413@lists.php.net to get a copy of this message | ||
* Alexey Borzov wrote:
> Solution: set a (reasonable) deadline, after which all "stable" packages
> not having documentation will be automatically demoted to "beta".
> Explicitly forbid marking the package stable if it does not have
> documentation.
Is there now a 'standard' for documentation? Couldn't see anything
on the PEAR manual after a quick view. Are there any documentation
templates that a developer could use?
Provide an "author's SDK", a .tgz or .ZIP with all kinds
of templates for classes, documentation, perhaps unit
tests and a skeleton PEAR package, some kind of automatic
tools to verify if a PEAR package complies to the standards
(or complies to the standards for PFC etc.).
Make the life for new PEAR developers the easiest way. To
gain a high momentum and acceptance, PEAR has to provide
a standardized set of tools and documentation to the developer.
--
Schnellanbindung an 350 Standorte?! CaseStudy anfordern unter:
transaktionsserver@emailseminar.de
ThinkPHP / rent-a-phpwizard bjoern@thinkphp.de
Sedanstraße 27 Tel: 0931 / 78 43 804
97082 Würzburg Fax: 0931 / 78 43 795
http://www.thinkphp.de/ http://www.rent-a-phpwizard.de/