Sylvia Greenberg wrote:
Hello. My name is Sylvia. I live in Maryland. I am an experienced trainer
and writer who uses technology daily, including Microsoft Office, iPhoto,
iMovie, and GoogleDocs.
My previous jobs include training adults in a business setting, training
teachers in K-12 education, and software documentation. Now that my three
children are getting older, I am looking for ways to write again and
volunteering to document Apache OpenOffice seems like a good fit.
Apache OpenOffice is new to me, but I have used, written about, and trained
people to utilize similar software in the past. I use Macintosh at home and
have easy access to a fast internet connection.
I look forward to working with you.
Sylvia
Welcome Sylvia!
Your experience will be a great help for the project!
The user documentation is being worked on the wiki, so you need to get
an account. For more details, see this page
http://openoffice.apache.org/orientation/intro-doc.html.
You can also add your info to this wiki page:
https://cwiki.apache.org/confluence/display/OOOUSERS/Documentation+Volunteers
The draft for the 4.0 user guide is growing here:
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". Note that this
guide is aimed to AOO 4.0, so you need the last version to check the guide.
Clearly, writing an user guide implies not only writing skills but also
knowledge of the software: if you have any doubt about how Apache
OpenOffice works, just ask!
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.
We use this mailing list to discuss the changes. In general we can say
that the approach is
* small changes like fixing typos and formatting errors: just do it!
* new material: just announce it! Both at the beginning of your work
and when you are done.
* big changes like moving sections or rewriting existing material:
discuss first on the list!
Tester, editor or writer? You choose
Regards
Keith N. McKenna
---------------------------------------------------------------------
To unsubscribe, e-mail: doc-unsubscr...@openoffice.apache.org
For additional commands, e-mail: doc-h...@openoffice.apache.org
