diff --git a/_includes/header.html b/_includes/header.html index b6bfc9161..4337d033f 100644 --- a/_includes/header.html +++ b/_includes/header.html @@ -137,7 +137,7 @@ Mail List
  • - OBO + OBO Community Slack channel
  • diff --git a/docs/PrinciplesReviewWorkflow.md b/docs/PrinciplesReviewWorkflow.md index 4a40570de..9a4ac8676 100644 --- a/docs/PrinciplesReviewWorkflow.md +++ b/docs/PrinciplesReviewWorkflow.md @@ -5,7 +5,7 @@ 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). Most of the steps are done by the OBO Foundry Editorial Working Group (EWG). -For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal to the OBO Operations Committee. +For the following, steps 1-5 and 12-13 are internal to the EWG and steps 6-7 are internal to the OBO Operations Committee. 1. Discuss the principle during an Editorial Working Group (EWG) call. 2. Write up proposed revisions as a [GitHub issue](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/new?assignees=nataled&labels=attn%3A+Editorial+WG&projects=&template=obo-foundry-principles.md&title=Principle+%23%3CENTER+NUMBER+HERE%3E+%22%3CENTER+NAME+HERE%3E%22) (not a pull request). @@ -14,10 +14,11 @@ For the following, steps 1-5 are internal to the EWG and steps 6-7 are internal 5. If necessary, discuss changes made during the commenting period and finalize the text. 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. 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. -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. -9. Allow a two-week commenting period on the pull request. -10. If the feedback includes major changes or objections, re-discuss during an OBO Operations call and re-do any relevant steps indicated above. -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. -12. Add the new principle to the [Principles Summary](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/fp-000-summary.md) list and to the [Principles dropdown menu](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/all.yml). +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-3gs80gmrk-9yZT913GViLUg04pgE3wOA) and request public feedback. +10. Allow a two-week commenting period on the pull request. +11. If the feedback includes major changes or objections, re-discuss during an OBO Operations call and re-do any relevant steps indicated above. +12. 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. +13. Add the new principle to the [Principles Summary](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/fp-000-summary.md) list and to the [Principles dropdown menu](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/principles/all.yml). 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. diff --git a/docs/participate.md b/docs/participate.md index 5871cd454..4202843c7 100644 --- a/docs/participate.md +++ b/docs/participate.md @@ -8,7 +8,7 @@ The OBO Foundry is currently a volunteer-run organization. There are many ways t - Submit a bug report, question, or feature request to the [OBO Foundry issue tracker](https://github.com/OBOFoundry/OBOFoundry.github.io/issues) - Join the [OBO-Discuss mailing list](https://groups.google.com/forum/#!forum/obo-discuss) - Join the [OBO-Tools mailing list](https://groups.google.com/forum/#!members/obo-tools) -- Participate in the [OBO Community Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-1oq48ttk7-kKo0i6TwntYtAq~Jcjjg4g) +- Participate in the [OBO Community Slack channel](https://join.slack.com/t/obo-communitygroup/shared_invite/zt-3gs80gmrk-9yZT913GViLUg04pgE3wOA) - [Submit your ontology](/faq/how-do-i-register-my-ontology.html) to be considered for inclusion in the OBO Foundry - [Create a pull request to improve this website](/faq//how-do-i-modify-website.html) - Nominate yourself to [join the OBO Foundry Operations Committee](/docs/NewOBOFC.html) diff --git a/index.html b/index.html index 07363a4e0..5ed713a99 100644 --- a/index.html +++ b/index.html @@ -30,7 +30,7 @@

    Participate

  • Code of Conduct
  • Join the OBO mailing list - and the OBO Community Slack workspace + and the OBO Community Slack workspace