Gervase Markham wrote:
I wish you told me that when I first posted the fact that I needed help making the announcement. That's why I posted it: To get feedback to edit improve it before I sent it out. When no one complained about the generality of the message, I used it as it was.> Any other ideas on getting their attention?If you want them to do something, make what they have to do as explicit as possible. No-one finds time for a task like "review the status of all the documentation I'm responsible for and make a list of what updates are needed."
I'm not sure how to make it more specific than what I needed to do. Let me try.
Algorithm:
1) Make a list of URLs and titles of relevant documentation on mozilla.org.
2) For each piece of documentation:
A) record what needs to be updated.
With the state of documentation being what it is, it's impossible for 1 person to maintain a giant document of all the documentation in all mozilla related projects. It would be easier if someone in each project did the algorithm I outlined above and sent it to me, where I could compile all of the information into one web page.> Also, what do you think about making the documentation status page > contain a CGI form with easily updatable information? I have no idea whether it's possible to have non-static pages on www.mozilla.org. I don't know of any currently. Gerv
Morgan
