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


Hi Karl-Heinz, :-)

On Mon, Jan 24, 2011 at 01:10, Karl-Heinz Gödderz
<LibreOffice@gukk-online.de> wrote:
OK. the script left out vista.
and referred on the second page to OOoAuthors.

This is something that will be looked at during the course of proofreading.

but the question I tried to ask was: may anyone change this draft or is
someone special to ask for this corrections?

If you'd like to get involved in working on documentation, you'll be
most welcome. If you like, you can have a user account on the Alfresco
site, and then you will be able to get involved in the workflow there.
Or you can get involved in the development of an l10n workflow.

and how do fit alfresco with odf-authors? is this a second platform?

The SC took a decision at its last meeting to accept the Alfresco site
a part of its Web infrastructure, and to put it under a LibreOffice
sub-domain (probably alfresco.libreoffice.org).

Most/all active members of the LibreOffice documentation team now have
an account there, and a workflow has been developed for the English
documentation team.

A few members of the l10n community have already expressed interest in
using Alfresco. Probably more will also do so once they become aware
of its existence.

Certainly, Alfresco has many technical advantages to offer. See my
comments below:

IMHO, the odfauthors.org software is far from being an ideal tool for
the LibreOffice docs team.

A) The odfauthors.org software is a product of a past time, when
leading-edge systems like Alfresco had not yet reached maturity, that
does not have all the features and power of a full-blooded content
development system like Alfresco: a mature version control system;
powerful and sophisticated workflow management; powerful content
search capability able to search within the managed content; built-in
discussion system that lets you anchor a discussion on a particular
content object; easy updating and uploading of content from directly
within the LibreOffice applications, via the Alfresco plugin for
OOo/LibO; etc.

B) The odfauthors.org software is a hybrid, one-off, custom
application without any community taking its development forward. The
odfauthors.org system is a software dead-end, based upon a CMS that is
not very widely used, for which little technical support is available
except from a small group of developers. Alfresco has an entire
community behind it.

C) The odfauthors.org software does not have the capabilities of
Alfresco to cater to the LibreOffice project's future needs for a
sophisticated product that can integrate closely with the project's
other development systems. Alfresco can provide a powerful platform
for the production and maintenance of developer documentation: API
manuals, etc. The odfauthors.org software cannot compete with it
feature-wise: it is a fairly manual system that is now dated.

However, no-one going to be in any way obliged to use Alfresco, just
as no-one is going to be obliged to develop LibreOffice documentation
on the odfauthors.org site.

I think that you can say that, ultimately, LibreOffice project
contributors are going to make their own choice and vote with their
feet.

My own personal take on things is this:

I think that odfauthors.org is a great resource for smaller Open
Source projects that don't have the people, time or resources to
properly develop their own documentation.

In addition, I feel that the LibreOffice project naturally has a
common interest with odfauthors.org: the promotion of the ODF format.
And, as another Open Source project, notably one that promotes the ODF
format, we should be supportive of odfauthors.org.

But I think it's in the best interests of a major software project
like LibreOffice to have an in-house documentation team with in-house
expertise.

No matter what similarities there might be between OpenOffice.org and
LibreOffice right at present (odfauthors.org develops documentation
for OpenOffice.org), the two products are quickly going to diverge.
LibreOffice might as well start developing its own documentation team
and expertise now - especially considering the need, at a future time,
to develop comprehensive developer documentation for LibreOffice, in
view of rendering it truly open.

Alfresco has many essential features and capabilities for that.

I wanna help, but first I must get clear the
connections/conjunctions/chainings.

HTH.

David Nelson

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

Context


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.