Ryan Fulcher wrote:
2/24/2010
Hi everyone,
This is Ryan Fulcher, and I'm new to the Open Office documentation project
as of today. First, I'd like to thank you guys for being so quick to welcome
new folks and for making it easy to get involved.
A little about me: I'm currently working on my MS in Technical
Communication at NC State University, I have a dog named Augie, and I drive
a Volvo that's old enough to qualify for antique plates. My interests
include photography, illustration and graphic design, and contemporary
literature. I'm totally on board with all things Open Source, and I want to
help out any way I can. More specifically, I want to help further the
mission of the Open Office project, as I think OO is a great suite, one that
definitely gives the for-fee competition a run for their money.
Professionally, I have a bit of experience and a lot of training with
Technical Communication, and aside from that I have a lot of straight-up
experience with web design and development, as well as editorial experience
at all levels. I'd be glad to provide any work samples you guys might need.
Down to business: I'd like to request the role of author.
I'm looking forward to getting involved, and I hope to hear from you soon.
Best,
Ryan Fulcher
[email protected]
Welcome, Ryan. I've given you the Author role. Sounds like you will be
a great addition to the team. Most newcomers start by reviewing a
document from the Review List (visible in the lower left column after
you log in). You'll have to look for the ones in English. Right now
we're concentrating on updating the Writer Guide to OOo version 3.2,
completing the Calc Guide and writing the first draft of the Base
Guide. Let us know what most interests you, and whether you'd like to
review a chapter or several or just plunge into writing missing
material. I'm only intermittently available this week (back on deck
next Tuesday), but others can help answer any questions you may have.
--Jean
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
