Hello everyone,

I've been trolling for a short while, so I thought I'd add my skills to the
pile:

I work as resource coordinator/ educational program design (not
programming). My strengths are technical writing, documentation and
editing. I wouldn't consider myself a power user of the software, but I
will glady review any documents for structure, grammar, spelling, etc,
needed.

Thank you for the opportunity.

Kind regards,

Amber Lee

On Mon, Jan 28, 2013 at 6:41 AM, Rakesh Thakoordyal <rakesh...@rogers.com>wrote:

> Thanks - it looks like there are some issues on the backend when trying to
> create an account - I'll try again later.
>
> Rakesh T.
>
>
>
> ________________________________
>  From: Keith N. McKenna <keith.mcke...@comcast.net>
> To: doc@openoffice.apache.org
> Sent: Sunday, January 27, 2013 3:20:50 PM
> Subject: Re: [Discuss]Call for volunteers [Was: Re: Starting to build the
> user guide]
>
> Rakesh Thakoordyal wrote:
> > I'd like to take part in this project.  I'm lightly familiar with
> > Calc and have been using Writer as my main word processor for the
> > last few months (used to be Word).  I also wouldn't mind helping to
> > write documentation for the other products, would just need time to
> > familiarize myself with them.
> >
> >
> > I know that there is documentation for Version 3.3 already so would
> > this involve updating those docs for a newer version or is this a
> > complete re-write?
> >
> > Rakesh T.
>
> Rakesh;
>
> Due to licensing constraints on the 3.3 and earlier documentation the
> 4.0 documentation is being done as a complete re-write on the the mwiki
> under ALV2 license. To see the current stage of the drafts go
> http://wiki.openoffice.org/wiki/Documentation/UserGuide and take a look
> at them. Anyone can read the wiki anonymously; however if you want to
> edit pages you need an account. To create one click the "create account"
> in the top left corner of the page and fill in the form and submit it. I
> believe we are still enforcing a 4 day wait period after the account is
> created before being able to edit anything as an anti-spam measure.
>
>
>
> Regards
> Keith.
> >
> > ________________________________ From: Keith N. McKenna
> > <keith.mcke...@comcast.net> To:
> > doc@openoffice.apache.org Sent: Sunday,
> > January 27, 2013 1:50:20 PM Subject: Re: [Discuss]Call for volunteers
> > [Was: Re: Starting to build the user guide]
> >
> > RGB ES wrote:
> >> 2013/1/21 Rob Weir
> >> <robw...@apache.org>
> >>
> >>> <snip>
> >>>
> >>> Do we want to have a "call for volunteers" soon?  Or do you want
> >>> to make more progress first?
> >>>
> >>> -Rob
> >>>
> >>
> >>
> >> Today I'm at just four pages to end the first bare-bones draft for
> >> the Writer guide. Beside the fact that I can also write the draft
> >> for a Math guide I think it is time to think about a call for
> >> people that can fill the holes on what I wrote, check my clumsy
> >> grammar and start writing on those topic I cannot write (Calc,
> >> Base, Impress, Draw, Asiatic/complex layout language settings and
> >> macros).
> >>
> >> Maybe we can do the call on two steps, calling first on the forums
> >> and users mailing list for people with experience on the program
> >> (on the forums there are many experienced users) and only
> >> afterwards make a more general call: to write a complete user guide
> >> good will is not enough.
> >>
> >> What do you think?
> >>
> >> Regards Ricardo
> >>
> > I concur that we need to start doing a call for volunteers. A two
> > step approach that you describe sounds like a good way to start. I
> > have been going through the introduction sections making grammatical
> > changes as best that I can, but though English is my native language,
> > I am by no means a grammatical expert. We need to attract not only
> > people who can write, but also people who can proof read and edit.
> >
> > I also agree with your earlier statement that we need to agree soon
> > on an overall style so that editors and proof readers know what to
> > edit against, as well as authors to use from the start.
> >
> > Regards Keith
> >
>

Reply via email to