Gervase Markham wrote:
I have yet to find a wiki that is both structured and up-to-date. Well, I'd settle for #1.
Wikipedia? Granted, it's not the same as developer docs.
:)
User replies suffer from the same thing.
I don't agree - I've found them very useful in the MySQL docs. And, even if they aren't useful for readers, they are very useful for _authors_ in knowing where the docs are unclear or lacking.
Right. In the PHP docs they also very often give useful hints and code examples, I think they're very useful. And ofcourse, integrating good comments into the actual article is one of the main points of having them :). It is much easier to update an article based on notes and tips from users who have been working with the subject, compared to having one writer who has to think of everything by himself (which may not nessecarily be the things users are looking for, usually there are many aspects).
I by the way don't think that all comments are let through in PHP... Maybe a quick review process would be a good idea.
As I have indicated before, devmo drivers are well aware of the need for some kind of QA process and community feedback on the docs. But, others may correct me, we have agreed to the following order:
- get a site (target audience, editing, templates, structure)
- get some content
- get some idea of the process
- choose a tool to assist that process (which is what user comments or wikis are)
Axel _______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
