If the developers don't write the documentation, who should write it?
Especially since someone who can write the developer documentation
(Especially XPCOM) probably needs to develop for Mozilla for a while.
"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===
>
>
>
