These sounds like good solid steps we could actually take without 
constructing a grand plan. I'll poke around a bit with staff and see if 
there's some issue i'm missing

Mitchell



fantasai wrote:
> Mitchell Baker wrote:
> 
>>What do you mean by organizational structure?  A website organization? A
>>person?
> 
> 
> Here are some ideas - 
> 
>   - Find several trusted CVS commit-enabled people willing to check in
>     documentation changes and new documents within a reasonable amount
>     of time.
> 
>   - Create or update pages that explain
>      - how to make changes to an existing document and generate a 
>        patch with doctor
>      - and what *exactly* to do with a documentation patch or new
>        HTML document.
> 
>   - Create a to-do list of abstracts and/or outlines for documents that
>     need to be written (and corresponding Documentation bug numbers).
> 
>   - Either revamp or get rid of the existing documentation templates because
>     they're very, very poorly coded.
> 
>   - Delete the section starting with "Use indentation." in
>     http://mozilla.org/README-style.html and, if Dawn decides to
>     check in the patch for bug 152104, replace it with a section
>     on using <div class="section">.
> 
>   - Link all this information together with a page similar to
>     http://mozilla.org/hacking/nutshell.html and keep these pages
>     updated.
> 
>   This way, if I say "I want to write web-developer documentation, where
>  should I start?", you can point me to http://mozilla.org/contribute/writing/
>  and I can find out not only that I need to do something with Bugzilla and
>  a Documentation component and that there's no copyright policy as of December
>  1999, but
>    - what documentation needs to be written, and hence what I can write for
>      mozilla.org
>    - what format the document should be in
>    - where and how I can submit the document to become part of mozilla.org
>    - what I can do to fix errors in and/or update existing documents on
>      mozilla.org
>    - how I can help make existing documentation easier for visitors to find
>    - who will be happy to answer any questions I have
>    - and what I should do if no one acts on my work within X amount of time
> 
> ~fantasai


Reply via email to