openoffice-doc mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From RGB ES <rgb.m...@gmail.com>
Subject Re: Introduction
Date Thu, 20 Jun 2013 16:08:12 GMT
Welcome, Natasha!

More comments below

2013/6/20 Natasha Selvey <nyselvey@gmail.com>

> Hello,
>
> My name is Natasha Selvey and I would like to get involved in
> documentation at OpenOffice. I have a background in Document
> Control/Quality Systems but I enjoy writing technical documents. I am
> also currently learning Java, Python, HTML, CSS, and Javascript.
>
> I already read through the orientation modules and signed up for MWiki
> and CWiki. I would really appreciate some direction for helping out
> with documentation.
>

Perfect!

At the moment, the user documentation is being worked on the wiki. Please
look at where the draft for the 4.0 user guide is growing:

http://wiki.openoffice.org/wiki/Documentation/UserGuide

(there is a link to the "status page" at the end). There are several
missing pages and holes on the existing ones, but an easy start would be to
proofread the existing pages and check the information for "accuracy". Most
of the material there was written by a non native English speaker (me...),
so the actual text needs a lot of attention.

Clearly, writing an user guide implies not only writing skills but also
knowledge of the software: if you have doubts about how Apache OpenOffice
works, just ask!

Note that this guide is aimed to AOO 4.0, so there are instructions on the
guide that do not completely correspond to the stable builds (like "menu
Tools → Options → Apache OpenOffice": on 3.4.1 you'll find "OpenOffice.org"
there). You can find development builds for 4.0 here:

https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds#DevelopmentSnapshotBuilds-AOOSnapshotfullsets

So the "tasks" available are many, some of them already mentioned:

* Check spelling and grammar for existing pages (proofreading)
* Check if it is possible to reproduce what the guide suggest, i.e., if
topics are clearly explained (accuracy and "understandability")
* Write new material

It is also possible to add

* User Guide "design": to make the user guide more visually "appealing" to
the readers.

Tester, editor or writer? You choose :)

Regards
Ricardo


>
> -Natasha Selvey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: doc-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: doc-help@openoffice.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message