|
| 1 | +## Overview |
| 2 | + |
| 3 | +This document describes the governance of the Spin project. |
| 4 | + |
| 5 | +The Spin project consists of several codebases with different release cycles. These codebases include: |
| 6 | + |
| 7 | +- Core Spin: |
| 8 | + - [Spin](https://github.com/fermyon/spin) |
| 9 | +- SDKs: |
| 10 | + - [Spin Python SDK](https://github.com/fermyon/spin-python-sdk) |
| 11 | + - [Spin JavaScript SDK](https://github.com/fermyon/spin-js-sdk) |
| 12 | + - [Spin Rust SDK](https://github.com/fermyon/spin-rust-sdk) |
| 13 | + - [Spin .NET SDK](https://github.com/fermyon/spin-dotnet-sdk) |
| 14 | + - [Spin Nim SDK](https://github.com/fermyon/spin-nim-sdk) |
| 15 | +- Plugins: |
| 16 | + - [Spin Plugins Index Repository](https://github.com/fermyon/spin-plugins) |
| 17 | + - [Fermyon Platform Plugin](https://github.com/fermyon/platform-plugin) |
| 18 | + - [Spin Test Plugin](https://github.com/fermyon/spin-test) |
| 19 | + - [Cloud Plugin](https://github.com/fermyon/cloud-plugin) |
| 20 | + - [Spin Cloud GPU Plugin](https://github.com/fermyon/spin-cloud-gpu) |
| 21 | +- Triggers: |
| 22 | + - [Spin Command Trigger](https://github.com/fermyon/spin-trigger-command) |
| 23 | + - [Spin SQS Trigger](https://github.com/fermyon/spin-trigger-sqs) |
| 24 | + - [Spin Cron Trigger](https://github.com/fermyon/spin-trigger-cron) |
| 25 | + |
| 26 | +Each repository is subject to the same overall governance model, but has different teams of people (“maintainers”) with permissions and access to the repository. This is meant to increase diversity of maintainers in the Spin project and also increases the velocity of code changes. Major changes and features to the project including additions to the repository list above are to be proposed through the [Spin Improvement Proposal](docs/content/sips/index.md) process. |
| 27 | + |
| 28 | +## Spin Project Maintainers |
| 29 | + |
| 30 | +Project maintainers are responsible for activities surrounding the development and release cycle of a specific repository they own. Technical decisions for code resides with the project maintainers, unless there is a decision related to cross maintainer groups that cannot be resolved by those groups. Those cases can be escalated to the Spin Governance Committee (discussed below). |
| 31 | + |
| 32 | +Project maintainers do not need to be software developers. No explicit role is placed upon them, and they can be anyone appropriate for the work being produced. |
| 33 | + |
| 34 | +Project maintainers and emeritus maintainers for each project should be outlined in the MAINTAINERS.md file in the corresponding GitHub repository. |
| 35 | + |
| 36 | +Changes to project maintainers use the following: |
| 37 | + |
| 38 | +- A project maintainer may step down by emailing the mailing list. When a project maintainer steps down, they become an emeritus maintainer. |
| 39 | +- Project maintainers MUST remain active on the project. If they are unresponsive for > 3 months, they will lose project maintainer-ship, unless the remaining project maintainers of the given project and the Spin Governance Committee agree to extend the period to be greater than 3 months. |
| 40 | +- New maintainers MUST be nominated by existing maintainers. Maintainers are to discuss and agree in a private setting adding a new maintainer. Once a descision has been made, a maintainer may be added to the project via a pull request to the relevant MAINTAINERS.md file. |
| 41 | +- A maintainer may be removed for a [code of conduct](CODE_OF_CONDUCT.md) violation by the Spin Governance Committee. Code of conduct violations may be submitted to any member(s) on the Spin Governance Committee by email. See email information on MAINTAINERS.md. |
| 42 | +- When a project has no active maintainers, the maintainers of the [fermyon/spin Github repo](https://github.com/fermyon/spin) become responsible for it, and may archive the project, or find new maintainers |
| 43 | + |
| 44 | +## Spin Governance Committee |
| 45 | + |
| 46 | +The project maintainers for [github.com/fermyon/spin](http://github.com/fermyon/spin) also serve as the Spin Governance Committee and have the following additional responsibilities: |
| 47 | + |
| 48 | +- Maintaining the mission, vision, values, and scope of the project |
| 49 | +- Refining this governance document |
| 50 | +- Making project level decisions |
| 51 | +- Making decisions about project licensing, contribution requirements, and other legal matters |
| 52 | +- Resolving escalated project decisions when responsible project maintainers are blocked |
| 53 | +- Managing the Spin brand |
| 54 | +- Managing access to Spin assets such as source repositories, hosting, project calendars |
| 55 | +- Handling code of conduct violations for any repository under the Spin project |
| 56 | +- Deciding what sub-groups and repositories are part of the Spin project |
| 57 | +- Overseeing the resolution and disclosure of security issues |
| 58 | +- Managing financial decisions related to the project |
| 59 | + |
| 60 | +In addition to the responsibilities listed above, this group is also responsible for bootstrapping a multi-stakeholder steering committee of 5-7 people to govern the project. The group is responsible for creating a steering committee Charter and shaping and executing the processes around selecting committee members. Once a steering committee is in place, the Spin Governance Committee will be dismantled and replaced with the Spin Steering Committee. The Spin Steering Committee should then establish additional governance structures as it sees fit (e.g., a Code of Conduct Committee for project moderation). |
| 61 | + |
| 62 | +The Spin Governance Committee have to match the following criteria: |
| 63 | + |
| 64 | +- Spin Governance Committee members MUST remain active on the project. If they are unresponsive for > 3 months, they will lose membership, unless the remaining members of the committee agree to extend the period to be greater than 3 months |
| 65 | + |
| 66 | +The Spin Governance Committee will select a chair to set agendas, call meetings, and oversee the decision making process. |
| 67 | + |
| 68 | +## Decision Making |
| 69 | + |
| 70 | +The default decision making process is objection-free consensus. In other words, a decision is made when all decision makers have had time to consider the decision and do not raise any objections. Silence on any consensus decision is equivalent to non-objection. Explicit agreement may be stated at will. |
| 71 | + |
| 72 | +Decision making scenarios MUST be promoted appropriately by the maintainer or committee member overseeing the issue. All substantial changes in any part of the Spin project including for governance related changes require a SIP. |
| 73 | + |
| 74 | +All substantial changes to governance require a supermajority quorum on the governance committee. |
| 75 | + |
| 76 | +In the extreme case that objection-free consensus cannot be reached after a reasonable amount of time and effort between project maintainers on a project level decision, a project maintainer can call for a [supermajority](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote) vote from the project maintainers for a repo on a decision. If quorum cannot be met for a decision, all members of the Spin Governance Committee are added to the relevant vote. |
| 77 | + |
| 78 | +If a decision impacts multiple repositories or requires a coordinated effort across multiple repositories and project maintainers are unable to reach a decision on their own for the relevant projects, a maintainer can call for a decision from the Spin Governance Committee. |
| 79 | + |
| 80 | +In the extreme case that objection-free consensus cannot be reached after a reasonable amount of time and effort on the governance committee, a committee member can call for a supermajority vote form the committee. If another member seconds the vote, the vote MUST take place. |
| 81 | + |
| 82 | +## Glossary |
| 83 | + |
| 84 | +- Objection-free consensus: A decision is made when all decision makers have had time to consider the decision and do not raise any objections. Silence on any consensus decision is equivalent to non-objection. Explicit agreement may be stated at will. |
| 85 | +- Supermajority: Two-thirds majority where at least two-thirds of the group is in favor of the decision being made. More context [here](https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote). |
| 86 | +- Emeritus Maintainer: These are project maintainers that are no longer active. We model this after the Helm Emeritus Maintainer role. More context [here](http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html). |
0 commit comments