John Keiser's document seems to serve a very different purpose from theI'm new here as well, and that seems to be the problem. There is no one to tell you what to do or where to start. My suggestion is to search through last month's email and fix what people are complaining about. Or, find a page on mozilla.org that could use an update, and file it as a bug on bugzilla.This is a well-known problem we discussed a month or two back. As I recall, the consensus was to do three things to make contributing documentation easier:1. Create a "map" of topics and available documentation with information about how accurate and up-to-date it is so we know what needs documenting and updating. Some conversants also suggested esignating an "editor" who can manage the process and assign tasks. 2. Find a couple of people willing to apply docs updates filed into Bugzilla to the site. 3. Write documentation about how to use Doctor, the web tool for making and applying changes to the web site. Of these three tasks the first is probably the most important. The only existing information of this type is way out-of-date: http://mozilla.org/docs/mdp/docstat.html Alex Vincent has been working on an updated version of this document, but I'm not sure where he's at. <ajv>Actually, that's John Keiser, with the Gecko Document Map. http://moz.zope.org/Members/jkeiser/gecko_doc/document_map. I've mainly focused on coordinating, and (2) is more in my alley (though we're trying to use moz.zope.org instead of Bugzilla as a primary focus -- b.m.o we're thinking of for tracking purposes primarily.) Alex</ajv>
http://mozilla.org/docs/mdp/docstat.htmlMyk mentioned above. Keiser's document seems to be an explanation about how different parts of Mozilla works together, while docstat.html is a list of what documentation needs to be updated. Does docstat.html have enough value for me to continue updating it? Or should I spend my time on some other project?
Morgan
Note: Check out docstat.html's status on http://stuwww.tcu.edu/~melandry/docstat.html .
