[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-documentation] Introducing myself

G'day, I just wanted to introduce myself. My name is Hal Parker, and I'm a
retired technical writer from Australia. I'm interested in working on the
user guides.

I understand that at least for the LibO3.3 release we are using the OOo3.3
docs as the starting point, and that Ron has created a template and applied
it to the chapters of the OOo Getting Started book, but I'm not sure how to
tell who is working on what or whether I have the latest version of a
chapter. Is the wiki page for Documentation/Development kept up to date?

Why aren't we using the OOoAuthors website for tracking development? It
seems well set up for that, and a lot less confusing (at least for me) to
tell what the latest version of a chapter is.

I find the Documentation section of the wiki very confusing. Would anyone
mind if I make some changes so things are easier to find? I know it's a
wiki, but being a newcomer here I don't want to tread on anyone's toes.


Unsubscribe instructions: E-mail to documentation+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/documentation/
*** All posts to this list are publicly archived for eternity ***

Re: [libreoffice-documentation] Introducing myselfDavid Nelson <commerce@traduction.biz>
Re: [libreoffice-documentation] Introducing myselfJeremy Cartwright <vardomescro@gmail.com>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.