RE: [PEAR-DEV] package pages
| From: | Michael Dransfield | Date: | Mon, 07 Oct 2002 13:33:35 +0000 |
| Subject: | RE: [PEAR-DEV] package pages | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-9919@lists.php.net to get a copy of this message | ||
At 15:20 07/10/2002 +0200, Lukas Smith wrote:
From: LIMBOURG Arnaud [mailto:arnaud.limbourg@cegetel.fr] Sent: Monday, October 07, 2002 3:17 PM So the matter is more that things should be made clearer on how to proceed. Docbook is pretty versatile, images are managed in docbook so it's possible to have screenshots and other cool stuff ;) the point is not the replace efforts to provide documentation in docbook form, but rather to give an option for all content that has not been ported or is too short lived to make sense to keep in the manual (like todo lists)I agree, but there is also a lot of confusion about where and how to write documents. For example, I was under the impression that the comments in our code would be extracted to form the docs on the pear website, then I find out that I need to copy this into docBook format (something I know next to nothing about), then there is a doc directory which contains html, txt and any other format that the author felt like using. One of the main benefits of php is the great documentation, I wouldnt like to see this lost with pear. Oh, and I agree that a project page would be nice (for PEAR developers), so long as it wasnt a replacement for good documentation.
regards, Lukas -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php