Le 2010-11-03 20:38, Jean Hollis Weber a écrit :
On Wed, 2010-11-03 at 09:20 -0400, Marc Paré wrote:
Le 2010-11-02 23:14, Jean Hollis Weber a écrit :
Also do you know if the developer docs have a workflow page and could
you point me to this page?
I don't know, sorry. Someone who has worked in that area might know.
Clayton (the other OOo Docs Co-Lead and an Oracle employee) oversees
that area. I do know the developer docs are wiki-based and are edited by
a variety of people. I have no idea how much updating is needed.
Hi Jean:
Thanks for the answer. A lot of things to keep track of.
Maybe Carlos could take a close look at your response here and see if
his list of Drupal modules complement your working needs. It sounds like
the documentation could all fit in well on the Drupal site. There will
obviously be a short learning curve and one of the Drupal dev may have
to lend a hand for a while till the website team has tweaked the site to
your needs.
I've already come back twice to this response and still can't imagine
how well you and the documentation team have done with such a load.
Congrats to all of you.
Marc
Here is the info on how the developer docs are handled at OOo:
- Clayton monitors the Admin, Basic, and Dev guides for edits.
Depending on who made the edit, he will either just leave the edit as is
(if it's from a known contributor) or validate the edit (if it's from an
unknown contributor).
- With each release of OOo, he reviews the edits on the Basic and Admin
guide. The Dev guide will only get a cursory review due to its size.
- There currently is no publish cycle for the Dev Guide... mainly due
to its size (+/- 2000 A4 pages)
- With each _major_ release, Clayton packages up the Admin Guide and
Basic Guide in ODT and PDF formats - he generally doesn't do this for
point releases. The Admin Guide and Basic guide have, historically, been
translated by Sun (into about 6 other languages), so part of the
release process included preparation work so that the Sun translators
could extract the Wiki content and translate it.
- The community contributions for the Dev Guide are different from
the contributions for the User Guides. The Dev Guide is more or less
a collection of concepts, not a book you want to read from cover to
cover. In the Dev guide, the contributions come almost 100% from
Sun/Oracle developers. External contributions are rare.
So, there's not much of a release process in place. The nature of the
development documentation is that it's a continuous evolution, and
not so fixed to each specific release of OOo.
--Jean
Thanks for the help with this Jean. We will take a close look at this as
well. It is always nice to get this type of feedback/information by an
obviously interested and well-informed individual.
Many thanks again for this information.
Marc
--
E-mail to [email protected] for instructions on how to
unsubscribe
List archives are available at http://www.libreoffice.org/lists/documentation/
All messages you send to this list will be publicly archived and cannot be
deleted
