I think---I know---that there are tech writers who are capable of writing about XPCOM. As a doc manager, I'd be thrilled if I could hire more writers to handle the many tasks. But that's not likely to happen anytime soon. And, alas, getting the engineers to write is difficult, to say the least. But I'm still hopeful that there are those in the Moz community that have the skills to take on, e.g., the task of writing about XPCOM. Trolling the lists of volunteers at the Open Source Writer's Group site might turn up some volunteers---I haven't been to the site in a while, but I know writers with engineering backgrounds have posted their volunteering offers there in the past. NeTDeMoN wrote: > I doubt a writer has the technical knowlege to document XPCOM, except in a > rare occasion. Part of being an engineer is the ability to write technical > documentation. That is why, when you take an engineering degree, you are > required to take writing courses. Mozilla 1.0 is not going to be the end of > the project. It is going to go on after that. As for the current process, in > my opinion - it sucks. There is not a documentation, and the documentation > that is around is outdated and incomplete. If developers don't like writing, > then in my opinion - tough! They should do it anyway. Either that, or there > needs to be technical writers hired to learn how it all works and write > about it. But, I have more faith in the documentation being correct if a > developer writes it. The developers don't have to spit out a glossy piece of > work, either. They just have to spit out something that someone else can > make glossy. > > "Michael Tulloch" <[EMAIL PROTECTED]> wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > Uhm. You don't put doc writing chores on the backs of thoe who program > > for a living...especially since many programmers have a revulsion to > > writing (few and far between are those souls who grasp > > that writing and programming are near kin because they are both are > > expressions of language). If you mean just to get things down, even > > then it's too late -- the code's already written; sentiment will be > > "My job's done here." The current process (speaking from what I've > > been reading here on the mailing list) seems to be much better -- you > > get involved as the code's being written; you describe the > > architecture and define your terms again, as much as is possible, as > > early as you can. Much better to leave the writing to those who well, > > got their degrees in that, and actually like doing it....:) > > > > ~Mike > > On Tue, 29 May 2001, NeTDeMoN wrote: > > > > > I thought of an idea. Why not freeze Mozilla for two weeks after Moz > 1.0's > > > release in order to write developer docs? That will give developers time > to > > > document because normally they are too busy. > > > > > > > > > > > > > > > > ---Mike > > =====CALLING ALL PATRIOTS==== > > Now is the time! Justice and liberty hang by a thread! > > Log on to freerepublic.com and make a difference! > > =====CALLING ALL PATRIOTS=== > > > > > > -- Steve Rudman Manager, Information Design Group Netscape Communications [EMAIL PROTECTED] 650-937-5006
