You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update Slack link
to the one that actually lets you join w/o an invitation (hopefully this won't attract spam)
* Update Slack link; minor wording change to intro
Update Slack link to the URL that actually lets you join w/o an invitation (hopefully this won't attract spam)
* Update Slack URL
Use URL that actually lets you join w/o an invitation (hopefully this won't attract spam)
Copy file name to clipboardExpand all lines: docs/PrinciplesReviewWorkflow.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ layout: doc
3
3
title: Principle Review Process
4
4
---
5
5
6
-
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 (EWG).
6
+
This page describes the process for reviewing, updating, and creating [OBO Foundry Principles](http://obofoundry.github.io/principles/fp-000-summary.html). Most of the steps are done by the OBO Foundry Editorial Working Group (EWG).
7
7
8
8
For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal to the OBO Operations Committee.
9
9
@@ -14,7 +14,7 @@ For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal
14
14
5. If necessary, discuss changes made during the commenting period and finalize the text.
15
15
6. Once the EWG agrees on a final version, a member presents the text to the OBO Foundry Operations Committee for discussion during a meeting or via the issue tracker.
16
16
7. Once the wording is approved by OBO Operations, a member of the EWG makes a pull request reflecting the consensus of previous discussions. Note that the pull request should be marked as 'draft' if it is a new principle.
17
-
8. For new principles or major changes to existing principles, announce the proposal on the [obo-discuss mailing list](mailto:obo-discuss@googlegroups.com) and the [obo-community #general Slack channel](https://app.slack.com/client/T01BAB621JR/C01BDKWDS91) and request public feedback.
17
+
8. For new principles or major changes to existing principles, announce the proposal on the [obo-discuss mailing list](mailto:obo-discuss@googlegroups.com) and the [obo-community #general Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-1oq48ttk7-kKo0i6TwntYtAq~Jcjjg4g) and request public feedback.
18
18
9. Allow a two-week commenting period on the pull request.
19
19
10. If the feedback includes major changes or objections, re-discuss during an OBO Operations call and re-do any relevant steps indicated above.
20
20
11. At the end of the commenting period, assuming no major changes are needed, a member of the EWG will merge the pull request (removing 'draft' status if appropriate) and thereby make the changes public.
0 commit comments