Brant Langer Gurganus wrote:
> Primarily web developer/evangelism documentation and end-user
> documentation. Since I am not on the developer side of things with
> Mozilla. I could do little more than proofread those documents.
OK. Just checking The impression I got was that all documen
... and for the string doc, this didn't work.
People should use their own server for preliminary docs or drafts,
nothing sounding like it had current mozilla docs.
Stage it on www.mozilla.org, file a bug, and link it when it's ready.
But don't make people compare two versions of one document on
> * I don't think we want a low barrier to entry. We want documentation
>to be written by people who know what they're talking about, namely,
>the developers. The developers know how to use CVS, so it's one
>fewer thing to learn.
"The developers" have had several years to produce d
> *Your privelidges can and will be revoked if you abuse them. Do not
> modify browser bugs if you are not a developer! Do not modify bugs that
> belong to other people! If you are in doubt, add a comment to the bug
> and do not actually modify it. We recommend following somebody else for
> a
On Monday 2002-07-08 17:30 +0100, Gervase Markham wrote:
> > * I don't think we want a low barrier to entry. We want documentation
> >to be written by people who know what they're talking about, namely,
> >the developers. The developers know how to use CVS, so it's one
> >fewer thin
L. David Baron wrote:
I was maintaining / helping to
> maintain those sites as if they were prominent, only to discover later
> that my time was wasted because they were no longer easy to find.
They were never easy to find. mozilla.org/docs/index.html is a
nightmare. It's almost completely
On Monday 2002-07-08 14:23 -0700, Asa Dotzler wrote:
> L. David Baron wrote:
>
>
>I was maintaining / helping to
> > maintain those sites as if they were prominent, only to discover later
> > that my time was wasted because they were no longer easy to find.
>
> They were never easy to find.
L. David Baron wrote:
> I suggest encouraging the people who should be writing documentation to
> write it, and once they've written it, to share it. I think the most
> successful group at getting people to write documentation is the
> organizers of the Monday night techtalks at Netscape, which h
Brian Heinrich wrote:
> Yes, the intent is to include dev docs. In fact, developer
> documentation/technotes seem right now to be the biggest thing in favour of
> using Zope in the manner suggested. . . .
I fail to see how that is in favor of Zope As dbaron said, anyone
capable of really
fantasai wrote:
> Are you saying that FTP and form inputs present for these others
> a higher barrier to entry than CVS?
As someone who once had to extensively use Zope for development of a
Zope-based web interface, I must say that this statement is precisely
true. Briefly:
1) The FTP inter
On 08 Jul 2002, it is alleged that Boris Zbarsky sauntered in to
netscape.public.mozilla.documentation and loudly proclaimed:
> Brian Heinrich wrote:
>> Yes, the intent is to include dev docs. In fact, developer
>> documentation/technotes seem right now to be the biggest thing in
>> favour of
L. David Baron wrote:
>
>>An observation that demonstrates that current site doesn't work for
>>everyone: there are so many sites about Mozilla (for example
>>mozilla-evengelism.bclary.com or mozdev.org, which hosts _documentation_
>>projects) that are not on mozilla.org
>
>
> Have you asked
On Monday 2002-07-08 21:00 -0400, Bob Clary wrote:
> I came to you with what I considered to be a straw man proposal on how
> to develop more web developer documentation on www.mozilla.org. There
I was under the mistaken impression (through an intermediary, from whom
I first heard about the pro
L. David Baron wrote:
> On Sunday 2002-07-07 19:58 +0200, Fabian Guisset wrote:
>>Documents written will of course never be lost (unless they are
>>desperately out of date).
>
> Will links be broken? That's just as bad.
There's no reason links should ever break if a smart developer works on
t
14 matches
Mail list logo