Alexander J. Vincent wrote: > I'd like feedback on this text before I submit it to MozillaZine for > general viewing. Opinions and the occasional flame are invited. > > imajes has requested we mention PHP as a possibility; I think that's a > bit premature. > > <text> > Documentation efforts for mozilla.org are under the microscope right > now, and we need some help. We have two main foci: the policies for > documentation and developing tools for documentation. > > In the n.p.m.documentation newsgroup, there are several healthy debates > on policies for mozilla.org documentation going on, but we invite all > interested parties to deposit their two cents, so we can have a set of > policies worth their weight in gold. > > Regarding tools, we have a serious shortage of people willing to develop > them. Perl and/or possibly Python skills are particularly needed. (The > shortage is great enough where we're really unable to actually put new > ideas on the table.) > > As for the documentation itself... we are not yet ready in our opinion > to have an all-out push to organize, edit and write documentation on a > large scale. Nonetheless, we invite everyone to keep their eyes peeled > and to help out in any way they can. Even without the large push, I'm > sure a few of us would welcome some help with what we have now. >
I don't see the use of this post until you have some suggestions for people. My two cents: put in something generally about what sort of tools need to be developed, what problems need to be solved. If you need to do something now, list what sort of tools (not too specific but not too general either) need developing and specifically start asking for people who want to write end-user (or whatever it's called :) and web developer documentation. Or alternatively, it could be a short blurb: "we don't know what we need to do for documentation but we know we need to do it! Come discuss with us! Perl hackers for tools welcome! Tech writers with a hankering to help Mozilla, come on down!" It's my intent to publish a call for developer info once I get this Wiki working (hopefully soon), but I'm not going to do it until I have some experimental tools ready and gotten some feedback from the kind folks here first. Preparation is essential. --John
