Skip to content

[SOP Review] Review due: 'GDI-SOP0002_ncps-veto-edic-decision.md' #69

Description

@github-actions

Summary

The SOP 'GDI-SOP0002' is due for review and potential revision.

Motivation

Part of the SOP life-cycle is the periodic review process. After '365' days (defined at .github/workflows/review_reminder.yml) since the last entry in the Document History, every SOP has to be formally reviewed, to make sure that the SOP is still relevant and up to date. Find more information inside the Charter and ISM documents.

Based on the information in GDI-SOP0002_ncps-veto-edic-decision.md, it was last reviewed/edited on 2024-10-29. This falls beyond the period of '365' days ago set as threshold for SOPs to be reviewed.

Required action

  • Review document GDI-SOP0002_ncps-veto-edic-decision.md. This includes, but not limited to: appointing relevant reviewers within the GDI network, bringing the SOP up for discussion within GDI, reviewing that the SOP is still relevant, reviewing that the SOP complies with the styling guide...
  • Modify the SOP document based on the review. For any content modification of the SOP, follow a similar approach as the one described in GDI-SOP0007.

Reminders:

  • Remember to link this GH issue with the respective PR (i.e., copy-paste the PR URL as a comment below).
  • Remember to add the review/revision row to the Document History. Even if no change was required, once the review is finished, add the proper row to the Document History of the document. This will aid with the automatic review detection and help the maintainers know which SOPs were reviewed and by whom.

Disclaimer

This GitHub issue was created automatically through the execution of scripts/check_sop_reviews.py, likely triggered through the GitHub workflow .github/workflows/review_reminder.yml.

  • To stop this behaviour, remove the automatic trigger (i.e., delete 'schedule' from the workflow file). Only do so if you are sure that this automatic review trigger is wrong.
  • If this automatic trigger was a fluke, it may be due to the Document History of this SOP being malformed (e.g., recent entries being added at the bottom) or other SOP-review GitHub issues not being named correctly (e.g., the SOP ID should appear in the title).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    SOP-reviewRelated to the periodic review of an SOP

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions