Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


I've been watching the feedback, including Jean's of course. Although
some months ago my own feelings were that the LibO English docs team
didn't really need a specific team leader, my opinion has somewhat
evolved since then.

This is partly because of the small number (or even practical
non-existence) of regularly active team members. New people have
turned up, done some work and then become inactive again. People
previously involved in OOo and ODFAuthors have sometime put in some
work and then gone silent again - sometimes leaving their work in a
half-finished state.

There are only a couple or so people with any accurate idea of the
state of play of docs work and who's doing what, and Jean is one of
them. Also, I have noticed how there is more general activity from
other people when Jean herself is in an active period, and how things
go largely dead when she's busy with other stuff in life.

So I do think it would be worth properly naming her team lead, because
she does seem to carry a lot of weight with people and since it could
give her a better position to be an ambassador for LibO documentation
(for recruiting new members, for possibly finding alternative ways of
getting documentation written for the project, etc.).

I'd see her as having more of an organizational/coordinating/project
management role, and as being more of a "librarian" than anything

"Possibly finding alternative ways of getting documentation written
for the project"?

Well, how about the possibility of getting commercial technical
documentation and translation agencies involved in
sponsoring/undertaking projects, in exchange for some form of
publicity/creditation for their contribs? That would, of course,
require some serious liaison and organization, and Jean would be a
well-qualified candidate for the job (if she felt able to take on the

This is just one idea that comes to mind, but I'm starting to think
that it's time to do some lateral thinking. The LibreOffice
documentation effort has currently ground almost to a halt in terms of
real productive work.

David Nelson

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.