[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] Calc Guide - Update and Review Process


Hi Kees,

Good question!

If we follow the process, then I think that the tracking spreadsheet will
already have enough information. A file should be ready for second review
if:
(1) The first review is complete, indicated by the relevant "Return date"
being populated.
(2) The author has moved the file from Feedback to Draft, indicated by the
Status column showing "In Draft".

Regards,

Steve


On Tue, 19 May 2020 at 08:10, <kees538@libreoffice.org> wrote:

> Hi Steve
>
> One question.
> How do we know a file is ready for a second review? Meaning the author
> has inspected the proposed changes and had accepts all. Should we add a
> notification in the Guide status sheet?
>
> Regards, Kees
>
> Stephen Fanning schreef op 18.05.2020 14:17:
> > All,
> >
> > To clarify my own thoughts and, hopefully, to help anybody else who
> > wishes
> > to be involved, I have tried to write down the steps involved in
> > updating
> > and reviewing one chapter of the Calc Guide. Please see below.
> >
> > (Please note that I am not intending to define the steps involved for
> > any
> > other guides!)
> >
> > If anybody feels that what I have written is illogical, or not in
> > accordance with the Team’s agreed procedures, then please let us know
> > through the mailing list.
> >
> > Regards,
> >
> > Steve
> >
> > --------------------------------------------
> >
> > (1) Initial update.
> > (a) Author copies master version of source file from relevant folder in
> > Nextcloud to own computer. The master version of the source file would
> > usually be found in the Published folder for the previous issue.
> > (b) Author enables recording of track changes and edits the chapter as
> > required.
> > (c) Author updates first part of file name to reflect issue of document
> > and
> > adds initials and date to file name (for example,
> > CG6408-PivotTables-SF-09May2020).
> > (d) Author copies updated file to Draft folder in Nextcloud.
> > (e) Author amends tracking spreadsheet to reflect status of updated
> > chapter.
> >
> > (2) First review.
> > (a) First reviewer amends tracking spreadsheet to indicate that he /
> > she is
> > performing the first review.
> > (b) First reviewer copies updated file from Draft folder in Nextcloud
> > to
> > own computer.
> > (c) First reviewer enables recording of track changes and reviews file.
> > This may result in edits to the text to fix problems or may involve
> > inserting comments that need to be addressed.
> > (d) First reviewer adds initials and date to file name (for example,
> > CG6408-PivotTables-SF-LMO-16May2020).
> > (e) First reviewer copies updated file to Feedback folder in Nextcloud.
> > (f) First reviewer amends tracking spreadsheet to reflect status of
> > updated
> > chapter.
> >
> > (3) Responding to first review.
> > (a) Author copies updated file from Feedback folder in Nextcloud to own
> > computer.
> > (b) Author inspects proposed changes and accepts all that are
> > acceptable,
> > discusses with first reviewer any significant rejections or comments
> > that
> > need resolution.
> > (c) Author accepts all changes to date and returns updated file to
> > Draft
> > folder in Nextcloud.
> > (d) Author amends tracking spreadsheet to reflect status of updated
> > chapter.
> >
> > (4) Second review.
> > (a) Second reviewer amends tracking spreadsheet to indicate that he /
> > she
> > is performing the second review.
> > (b) Second reviewer copies updated file from Draft folder in Nextcloud
> > to
> > own computer.
> > (c) Second reviewer enables recording of track changes and reviews
> > file.
> > This may result in edits to the text to fix problems or may involve
> > inserting comments that need to be addressed.
> > (d) Second reviewer adds initials and date to file name (for example,
> > CG6408-PivotTables-SF-LMO-KK-25May2020).
> > (e) Second reviewer copies updated file to Feedback folder in
> > Nextcloud.
> > (f) Second reviewer amends tracking spreadsheet to reflect status of
> > updated chapter.
> >
> > (5) Publishing.
> > (a) Author copies updated file from Feedback folder in Nextcloud to own
> > computer.
> > (b) Author inspects proposed changes and accepts all that are
> > acceptable,
> > discusses with second reviewer any significant rejections or comments
> > that
> > need resolution.
> > (c) Author accepts all changes to date and removes all initials and
> > dates
> > from the file name.
> > (d) Author returns updated file to Published folder in Nextcloud.
> > (e) Author amends tracking spreadsheet to reflect status of updated
> > chapter.
>
> --
> To unsubscribe e-mail to: documentation+unsubscribe@global.libreoffice.org
> 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
>

--
To unsubscribe e-mail to: documentation+unsubscribe@global.libreoffice.org
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

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.