incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jing Bai <>
Subject Re: Symphony documentation for AOO?
Date Fri, 17 Feb 2012 15:25:40 GMT
The wikis we use are xpages wikis that run on Domino servers. USA IDC hosts
the WIKI for all Lotus products, such as Lotus Connections, LotusLive,
Symphony, Sametime and etc. There is a STSM named John Hunt who wrote the
code to transform DITA into DXML (the xpages source code) for wiki pages.
Here is one demo on how we publish the product documentation in Wikis:

Publishing product documentation in wikis lets us provide accessible
documentation in a friendly and easy-to-use format where customers can
comment directly against topics and even update the instructions. Writers
can review that feedback and incorporate appropriate changes into source
files for the next product release. Using wikis lets IBM consolidate
product information while fostering a greater sense of community between
IBMers, business partners, and customers.
We may reuse the WIKI platform in USA IDC, setup one area for AOO if
necessary. I would like to ask USA IDC, if this is feasible.

On Fri, Feb 17, 2012 at 8:57 PM, Rob Weir <> wrote:

>  On Fri, Feb 17, 2012 at 4:19 AM, Andre Fischer <> wrote:
> > Hi Betsy,
> >
> >
> > On 17.02.2012 07:16, Jing Bai wrote:
> >>
> >> Greetings, I am Betsy Bai who leads the ID team in IBM Symphony team.
> >> Actually, it is not like that. "The product teams at IBM don't do their
> >> own
> >> doc."
> >
> >
> > [...]
> >
> >
> >> In the future, we would like to promote the WIKI help console to the
> >> community if appropriate. Since it is more collaborative, but to make it
> >> happen, the file format would be changed into DITA, if anyone is
> >> interesting in it, I would like to provide an article on its details.
> >
> >
> > I would like to hear more about a wiki base help system.  That sounds
> very
> > interesting and seems to fit quite well for an open source project.
> >
> > Is DITA an open format?
> >
> Yes, it is an OASIS Standard, like ODF is.   But instead of being a
> generic WYSIWYG format, it has high level support (a vocabulary) for
> technical documentation, with special markup to express tasks,
> concepts, reference material, etc., as well as support for conditional
> processing and inheritance.  So you can mark a paragraph as applying
> only to the Linux build, and another paragraph as applying to Windows
> only, and then when you publish, you could decide to include one or
> the other, or both.
> A conceptual overview is here:
> -Rob
> > -Andre
> >
> > [...]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message