incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: [User Documentation]Are there any plans in place or formal user documentation for AOO
Date Wed, 29 Aug 2012 19:16:23 GMT
On Wed, Aug 29, 2012 at 2:40 PM, Keith N. McKenna
<> wrote:
> Good Day All;
> Today I am going to venture into the breach and bring up a topic that in my
> experience is most developers favorite profanity: i.e. User Documentation.
> One of the major reasons I have used and promoted is its well
> written and easily available user documentation. I see a planning wiki for
> documentation with no activity since 2011.
> I also have gone through most of the archived mail to this list I could find
> on this topic with no apparent consensus on what to do. I have also tried
> the ODFAuthors website and mailing list. There appear to be some drafts o
> chapters or a getting started guide but that is about all. The response from
> the list was basically whatever you folks decide to do with them.
> My basic question is re there any plans for user docs or AOO and if so where
> would the information be found? Although I am not a tech writer and have no
> real experience in the publishing world, this is a area I believe that I
> could be o some small help in. I have done document review before on both
> software documentation and or internal corporate standards documents.

As far as I know, no one is working on documentation, beyond build
guides and release notes.

If you read through the past discussions you certainly saw that we got
caught up in license discussions.  The thing that got us stuck before
was the license on the legacy documentation.  It is not
Apache License or anything compatible.   So if we wanted to revise the
existing doc we'd need to do it outside of Apache, like with the ODF
Authors group.  That's were it left off.

But it might be a good time to revisit the question.  I think we have
a greater feel for the nuance about how the ASF thinks about license
compatibility.  (Or at least I know that there are sufficient nuances
that one should never say never).

In one sense this is the lowest of all the low-hanging fruit for
collaboration between OpenOffice and LibreOffice.  If would be really
easy to produce a doc set that would be common across the two
products.  A simple meta-notation could be defined for any
product-specific concerns.  These could be processed with the Apache
ODF Toolkit to create the product-specific output docs.

For example:

"Describe core feature here.

%%%IF LibreOffice%%%
Put LibreOffice specific content here...

Continue with common description"

Moving to DITA for the documentation would be even cleaner, since DITA
has built-in support for this kind of conditional processing.



> Regards
> Keith

View raw message