From c3c2d9e2403711652ba873b00688dc8a8b5ed870 Mon Sep 17 00:00:00 2001 From: "Darren A. Natale" Date: Wed, 13 Sep 2023 08:59:31 -0400 Subject: [PATCH] Update PrinciplesReviewWorkflow.md for clarity and fix typos --- docs/PrinciplesReviewWorkflow.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/PrinciplesReviewWorkflow.md b/docs/PrinciplesReviewWorkflow.md index 4f36465ba..a41d0e775 100644 --- a/docs/PrinciplesReviewWorkflow.md +++ b/docs/PrinciplesReviewWorkflow.md @@ -3,16 +3,16 @@ layout: doc title: Principle Review Process --- -This page describes the process for reviewing, updating, and creating [OBO Foundry Principles](http://obofoundry.github.io/principles/fp-000-summary.html). +This page describes the process for reviewing, updating, and creating [OBO Foundry Principles](http://obofoundry.github.io/principles/fp-000-summary.html) by the OBO Foundry Editorial Working Group. -- Discuss the principle on working group call +- Discuss the principle during a working group call - Write up proposed revisions as a GitHub issue (not a pull request) - Inform the Editorial WG via email that the ticket needs discussion (if it doesn’t happen automatically) -- Two-week commenting period on GitHub issue tracker +- Two-week commenting period on the GitHub issue tracker - Make any incremental improvements on the tracker -- When the Editorial WG agrees on a final version, discuss on an Operations Committee call or via the issue tracke +- When the Editorial WG agrees on a final version, discuss on an Operations Committee call or via the issue tracker - Make a pull request - Two-week commenting period on the pull request -- Upload final changes to OBO Foundry web site for public viewing. +- Upload final changes to OBO Foundry web site for public viewing The need for a new principle can arise when an existing principle tries to cover too much and requires splitting, or as new needs arise within the community.