|
| 1 | +--- |
| 2 | +title: "Governance and Decision Making" |
| 3 | +--- |
| 4 | + |
| 5 | +## Abstract |
| 6 | + |
| 7 | +_Scientific Python: Tools and Services_ is a consensus-based community subproject. |
| 8 | +Anyone with an interest in the project can join the community, contribute to the project design, and participate in the decision making process. |
| 9 | +This document describes how that participation takes place, how to find consensus, and how deadlocks are resolved. |
| 10 | + |
| 11 | +## Roles And Responsibilities |
| 12 | + |
| 13 | +_Scientific Python: Tools and Services_ has the following roles and responsibilities: |
| 14 | + |
| 15 | +### Community Members |
| 16 | + |
| 17 | +The _Scientific Python: Tools and Services_ community consists of anyone contributing to our tools or services, whether by contributing code, or by commenting on or reviewing others' contributions. |
| 18 | +Community members must adhere to our [code of conduct](https://scientific-python.org/code_of_conduct/). |
| 19 | + |
| 20 | +### Maintainers |
| 21 | + |
| 22 | +Tool / Service Maintainers are community members that have demonstrated continued commitment to specific tools or services through ongoing contributions. |
| 23 | + |
| 24 | +Maintainers are responsible for reviewing PRs to specific tool repositories, or for maintaining specific services. |
| 25 | +They have maintainer rights. |
| 26 | + |
| 27 | +For new tools and services, the Tool / Service Maintainer role can be assigned to any or all of the existing maintainers. |
| 28 | + |
| 29 | +### Steering Committee |
| 30 | + |
| 31 | +The Tools / Service Steering Committee members are maintainers that have demonstrated continued commitment to this Scientific Python sub-project through ongoing contributions. |
| 32 | + |
| 33 | +You can think of them as a "meta team", responsible not (only) for individual tools, but for accepting new tools and services, and reviewing tool/service related submissions to https://tools.scientific-python.org. |
| 34 | +They have maintainer rights. |
| 35 | + |
| 36 | +A new Tools / Service Steering Committee member can be nominated by any existing Steering Committee member. |
| 37 | +Discussion about new Tools / Service Steering Committee nominations is one of the few activities that takes place on the Tools / Service Steering Committee members' private discussion forum. |
| 38 | +The decision to invite a new Tools / Service Steering Committee member must be made by "lazy consensus", meaning unanimous agreement by all responding existing Tools / Service Steering Committee members. |
| 39 | +Invitation must take place at least one week after initial nomination, to allow existing members time to voice objections. |
| 40 | + |
| 41 | +## Decision Making Process |
| 42 | + |
| 43 | +The Tools / Service Steering Committee uses a _consensus seeking_ process for making decisions. |
| 44 | +The group tries to find a resolution that has no open objections among team members. |
| 45 | +Members are expected to distinguish between fundamental objections to a proposal and minor perceived flaws that they can live with, and not hold up the decision making process for the latter. |
| 46 | +If no option can be found without an objection, the decision is escalated to the [Scientific Python Community Leaders](https://scientific-python.org/about/#community-leaders). |
0 commit comments