On Monday 01 November 2010 18:34, Marc Paré wrote: > Thanks, I'll take a look. Is there anyway that someone on the > documentation team to sketch out the workflow. You have developed > this over a few years and we don't really have a workflow to work > with. This would help to demistify workflow.
Maybe the drawing I created some time ago[1] (according to the description given from Jean resp. the oooauthors list) can be helpful for discussion. Feel free to use or change it. Note, that it may be inaccurate or outdated. Verbal description (AFAIR): There are 2 main workflow pathways: A simple one for internal documents and another one leading to externally published documents. The internal path only has 2 states: draft & published internally. The external path includes 3 different document states: internal draft, pending review (which means, submitted for publication), published externally. Transitions are, of course, submission, publication, and retraction (the latter leading back to draft state[?]) L10N: Documents from any state might give rise to translation activities, which again would open the same (or a similar) workflow for the (now localized) document. The main 2 problems in the (folder based) Plone system IMHO was to find a document (where is the newest version?) and to get a quick overview over the project state (how many documents are in which state, how many untranslated documents, etc.). Hence, keeping track over the project had to be done mainly by a human (i.e. Jean ;-) ). Also missing are "minor" state informations e.g. "checked for software version X.Y" or "indexed" or "branding updated" or similar (which is a minor point but nice2have, and could be done e.g. by tagging). Nino [1] http://wiki.services.openoffice.org/wiki/User:Nnino/Drafts/Oooauthors_Workflow -- 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
