Alex
Specific suggestions for documentation from the session are below. Of
course, everyone bascially wanted more and better documents.
1. A document annotation system as discussed earlier, where
one could add a comment/edit at the end of a doc
viewers could see the comments even if the doc owner hasn't
revised he doc to include them
the comments would be delted after the doc owner has decided
what to do with the comment
2. Better (much better) indicators for out-of-date info.
3. A way for people to note errors, corrections, improvements without
needing to pull and build the CVS doc tree, and without having to get
CVS write access.
4. A way for the info in the weekly status reports to be more accessible.
Mitchell
Alexander J. Vincent wrote:
> Mitchell Baker wrote:
>
>> I've taken a a bit of a vacation, and am catching up on post 1.0
>> activity.
>>
>> Kudos to everyone who contributed to the Mozilla 1.0 launch documents,
>> they are awesome. I'm not sure how many people saw the blurb in the
>> New York Times about the 1.0 release. The blurb had an image, and the
>> image was the first page of "A Guide to Mozilla 1.0." It's great to
>> see, the Guide is an excellent overall introduction to the project. I
>> was astonished at the way the launch docs came together; Ralph and
>> Brian did some mighty work keeping things together in the last few days.
>>
>> I use the Guide and FAQ quite a bit to respond to questions, which to
>> my mind proves their continuing value.
>>
>> Mitchell
>>
>
> Well, hello there. :) I can't take any credit for the 1.0 Guide and
> FAQ; I dropped in on documentation after the fact.
>
> Sorry to change the subject on you, madame, but do you remember the Nov
> 9, 2001 Developer Day in Mt. View, the business meeting that you
> organized in the upstairs conference room? I've lost all my notes from
> that meeting (I wish I'd been awake enough to take good ones anyway),
> and I've been screaming for the last few weeks for confirmation and
> specifics on what the business community is asking for from documentation.
>
> We aren't entirely sure what they need, but I do know from that meeting
> that they do need it.
>
> Alex Vincent
> author, JavaScript Developer's Dictionary (Sams Publishing)
> http://www.jslab.org
> Vallejo, CA
>
