AW: [PEAR-DEV] [Call For Votes] PHP::Fork
| From: | Stephan Schmidt | Date: | Sat, 08 Nov 2003 15:39:31 +0000 |
| Subject: | AW: [PEAR-DEV] [Call For Votes] PHP::Fork | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23356@lists.php.net to get a copy of this message | ||
Hi,
> > You can't be serious!
> Adjust your tone. Thanks.
This was not meant as an insult.
In German it would translate to something like "Das kann doch nicht sein
Ernst sein?". I don't think that this is too harsh!
(See Klaus' post)
> "Documentation in an appropriate format (plain text, docbook)
>
> Your code must come with appropriate documentation in one of the
> following formats:
>
> - Docbook XML
> - Plain Text"
>
> (http://pear.php.net/manual/en/developers.contributing.php)
> It is pretty funny to see how much developers have actually read the
> "Developers Guide" ...
In the case of the PHP_Fork proposal docs generated by phpDocumentor
2.2.2 have been available. That means it should be no problem to
generate peardoc from the sourcecode.
In fact, I thought that this package is really well documented.
Regarding my packages, I always add inline docs and as soon as a package
is accepted I try to work in the online docs.
I do not have the time to do all work at once, and if I can't be sure
that the package is accepted, I'm not willing to write documentation
that no one will read.
Stephan
PS: If you need docs in text format, why don't we just use lynx on the
HTML version?