Le 2010-11-02 16:23, Jean Hollis Weber a écrit :
On Tue, 2010-11-02 at 13:03 -0700, Andy Brown wrote:
On Tue Nov 02 2010 11:30:21 GMT-0700 (PDT) Michael Wheatland wrote:
On Wed, Nov 3, 2010 at 3:43 AM, Carlos Jenkins<[email protected]> wrote:
I really think we are going to need a Dashboard on the website so users
can accommodate their work or interest on their dashboard.
Cheers
Note/Question: Should I cross-list?
Another question that needs to be asked, should we have a document
checkout for the workflow to ensure that only one person is working on
any given document at once?
The current setup has a "flag" that is set for "retract" to show that
someone else is working on the document, though it does not prevent
someone else from downloading.
Also how is community consensus reached as to when a document is ready
for external publishing?
A democratic review system for proposed changes on final review
documents should be pretty easy to setup (Voting API). For an example
on this type of system have a look at Ubuntu Brainstorm, slightly
different concept but could work just as well.
Thanks for the info so far.
There is no community consensus on when a document it ready for external
publishing. Right now, Jean Weber, the volunteer co-lead makes that
call. I see no problem with this setup as Jean has the expertise to
make the call, and I have seen no complaints from any other members. I
do not feel a vote would be in the best interest of the project.
Have a look at the www.oooauthors.org , on the entry page is a dcoument
called Introducing OOoAuthors it details how the project works.
Although people seem happy with me acting as "publisher" for the OOo
user guides, it really would be much better if each book had its own
coordinator/editor/publisher, both to spread the work around and so
people could cover for each other if someone is unavailable for more
than a few days (illness, travels, other work or family commitments).
The idea was to have an experienced technical editor (or similar) to act
in the role of coordinator/editor/publisher for each book, but the other
people who filled that role in the early days have moved on to other
things.
BTW, the OOo *developer* docs are not handled through OOoAuthors; those
docs are primarily wiki-based and the processes for review and approval
are different.
--Jean
Hi Jean
Thanks for your answers and all of the other documentation team answers.
This is really a lot of good information. If only there were enough
members to do all that we wanted. Let's hope that with LibO more people
will come on-board for help with the documentation team. I am guessing
the the US and Canadian have not really been tapped and I am also
guessing the Mexico is probably the same. Once we organise and market we
will hopefully get more people on board.
Could you tell me (I am also a the LibO Marketing Team member) how many
more members you would need at this point, what type of qualifications
they should have? Ideally, how many would the documentation team need?
Also do you know if the developer docs have a workflow page and could
you point me to this page?
Thanks again for all of your help. As you can tell the Drupal team
members are here to listen and to help out. Let us know if there are any
missing features that the documentation team would like to have or if
you would like a change in the workflow in the Drupal setup.
Cheers
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
