ccornell - OpenOffice.org wrote:
I guess I'd like to volunteer. I'm not a programmer, but I'm
comfortable with a computer. I currently have VISTA on a Dell
machine. Something like proof reading is my speed these days.
Frank
The easiest place to start is here:
http://wiki.services.openoffice.org/wiki/Documentation
Jean has been busy posting the User Guides for 3.x. They are in a
"Published" status, but still could really use fresh eyes looking them
over.
Since the docs are all available on the Wiki, it is quite easy to log
in, and edit a page. You can do this on your own schedule, with no
deadlines or other pressure. Even a single edit to correct a spelling
error is welcome.
Things to look for:
- spelling
- grammar
- consistency (looking even for those little things like the consistent
use of full stops on bullet lists)
- technical content (use your own experience and knowledge to improve
what's already written)
- missing content
You can do one of these things, or even all of them... whatever you're
comfortable with.
If you see something that requires a major rewrite, or missing info, you
can either make a note of it on the Wiki Discussion page, or raise it on
the [email protected] mailing list.
If you are comfortable with your knowledge on a topic, you can write a
draft (a HowTo, a FAQ, a Guide etc.). You can do it right on the Wiki
if you like. The rest of the Documentation team can help out with
shaping it into a complete document. If you would prefer to write
offline (outside of the Wiki) you can use the tools and guidelines
available on the OOoAuthors website at: http://oooauthors.org
We are also always looking for fresh ideas... things like screencasts,
new ideas for ways to organize and present things on the Wiki, or just
about anything else that comes to mind. Feel free to speak up, add your
thoughts and ideas.
The most important thing is to do what you're comfortable with.
C.
Well, after my move to a better handicapped apartment
(bigger for the same price)
I may be able to help with the Base Docs. Reading it and
try the info out to see if it makes sense to a user like me.
Tim L.
retired mainframe programmer and computer consultant
{ forced to after debilitating back injury and three strokes }
--------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
