[Copied from another thread. My comments below.] Olivier Hallot wrote:
——————— Other opinions: Yes I have one radically different. Rationale: the current workflow and available resources is incompatible (IMHO) with speed of software development, the gap between software release and Guide release is very hard to close. I prefer a dynamic "time-release" of the guides, as with the software. That means publish "as-is" at time of release, whatever is available, ideally synch'ing with the software release. Each update will be a "Revision number". I foresee usage of master documents to compile the book periodically and quickly, and chapters updated by trusted Authors. One coordinator per guide. Full usage of track changes and comments. A new challenge for sure, but I propose to select one of our guides and test the new workflow. Olivier —————————- My response: (1) The target audience for the user guides is ordinary users. Very few of them are familiar with the type of document release cycle described by Olivier. I think most of them are likely to be confused and unhappy with the resulting books. (2) The suggestion of book coordinators and “trusted authors” is excellent and certainly worth a try, but many years of experience tell me that finding enough people with the time and skills to do the ongoing work will continue to be a major problem. (3) Print copies of the books will be impractical to produce. I’ve been the person doing them through Friends of OpenDocument, but I won’t attempt to keep up with a quick release cycle. This may not matter to the project, but you need to be aware of this. Jean -- To unsubscribe e-mail to: [email protected] Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.libreoffice.org/global/documentation/ Privacy Policy: https://www.documentfoundation.org/privacy
