As most of you know, there is a great deal of uncertainty about the
future of OpenOffice.org, in particular future releases. Clearly there
will be a need for ongoing support from the community for the many
people running OOo, so we should finish the v3.3 user guides that we're
working on, but will there be a need for new updates? I don't know.

The main OOo website hasn't been loading properly for over a week
(although the wiki and the forums continue to work fine), so no one can
download the almost-finished OOo 3.4 unless they happen to know where to
find it on one of the mirrors. Is is worth the effort to work on user
guide updates for OOo3.4 until/unless we know that it will actually be
released to users? I don't know about you, but I don't think it's worth
my time to do so.

I do plan to see that the OOo v3.3 books are completed and published.
The OOo Impress Guide is almost done. I'm not sure what to do about the
Draw Guide, which Martin is updating to LibO 3.4, as there are some
differences between OOo and LibO. If anyone is keen to do an OOo 3.3
version of the Draw Guide, do say so on the list.

Those of you who are most keen on the user guides might consider moving
to the LibreOffice Documentation Team, which has been rebranding the OOo
v3.3 guides to LibO and will soon start updating them to LibO v3.4. The
LibO Docs team is also getting involved in blogging and planning other
ways to provide users with information. We're also in the process of
reorganising the Docs wiki and producing a Contributors' Guide for the
Docs Team.

If you're interested in joining the LibO Docs mailing list, send a blank
email to documentation+subscr...@libreoffice.org 

You can also read the archives or join the discussions here:
http://nabble.documentfoundation.org/Documentation-f1645240.html

--Jean


-- 
-----------------------------------------------------------------
To unsubscribe send email to authors-unsubscr...@documentation.openoffice.org
For additional commands send email to sy...@documentation.openoffice.org
with Subject: help

Reply via email to