LibreOffice Review Guide

Documentation
1

Document Review Process Using LibreOffice (LO) and Git

LibreOffice (LO) documents support track changes, but integrating this feature with Git and the Merge Request (MR) process can be challenging. Below is a streamlined procedure to review LO documents efficiently without generating unnecessary commits for enabling or disabling track changes.

Key Features of LibreOffice:

  • LO allows you to compare two documents and generate differences similar to track changes.
  • This method avoids additional commits for enabling/disabling track changes.

System Configuration

  • RockyLinux v8.10
  • LO v6.4.7.2

Document Editor Workflow

  1. Modify the LO Document
  • Make your changes to the document as needed.
  1. Create a Branch and Push to Git
  • Create a new branch for your changes.
  • Commit your modified document and push it to the remote repository.
  1. Submit a Merge Request (MR)
  • Create an MR for the branch containing your changes.
  • Ensure the MR is assigned to the appropriate reviewer(s).

Document Reviewer Workflow

  1. Download the MR Version of the Document

    • Using the GitLab web interface download a copy of the document with changes

  2. Ensure your OpenCPI is has the latest from the develop branch

  3. Open the Document from MR in LibreOffice

  • Open the modified document from the branch in LibreOffice.
  1. Compare Documents Using Track Changes
  • Navigate to Edit → Track Changes → Compare Document...
  • Select the base document (from the develop branch) for comparison.
  • This will display only the changes made, preventing unnecessary commits for enabling or disabling track changes.
  1. Review and Provide Feedback
  • Use LibreOffice’s track changes feature to review the modifications.
  • Accept or reject changes as needed, and add comments to the MR if required.

Notes

  • By following this process, you avoid additional commits for enabling/disabling track changes.
  • The comparison feature ensures that only the differences between documents are highlighted, making the review process more efficient.

This approach streamlines document collaboration while maintaining a clean Git history.