Skip to content

Commit 242a262

Browse files
committed
require supermajority quorum instead of vote
Signed-off-by: Michelle Dhanani <[email protected]>
1 parent 330c762 commit 242a262

File tree

1 file changed

+3
-19
lines changed

1 file changed

+3
-19
lines changed

GOVERNANCE.md

Lines changed: 3 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ The default decision making process is objection-free consensus. In other words
4747

4848
Decision making scenarios should be promoted appropriately by the maintainer overseeing the issue:
4949

50-
- tag maintainers in relevant issues / SIPs
50+
- tag maintainers in relevant issues and SIPs
5151
- send out mailing list reminders
5252
- communicate updates in meetings
5353

@@ -82,27 +82,11 @@ The Spin Governance Committee will select a chair to set agendas, call meetings,
8282

8383
### Decision Making
8484

85-
The default decision making process is objection-free consensus except for changes to the Governance of the project which requires a supermajority agreement of the committee. The process for making governance related changes is described below.
85+
The default decision making process is objection-free consensus. All governance related decisions require supermajority quorum. All substantial changes require a SIP. A substantial change is one that changes the project governance itself, instead of editorial changes providing clarifications, small bugfixes, etc.
8686

8787
Decision making scenarios should be promoted appropriately by the member overseeing the issue.
8888

89-
In the extreme case that objection-free consensus cannot be reached after a reasonable amount of time and effort,
90-
a member can call for a supermajority vote from the committee.
91-
92-
### Changes to Governance
93-
94-
The process for changes to the GOVERNANCE.md file is as follows:
95-
96-
1. Decide whether the change is substantial in nature. A substantial change is one that changes the project governance itself, instead of editorial changes providing clarifications, small bugfixes, etc
97-
2. Then,
98-
- For substantial changes:
99-
i. Open a new SIP for the changes
100-
ii. Follow the [normal SIP process](https://github.com/fermyon/spin/blob/main/docs/content/sips/index.md), requiring a supermajority for acceptance
101-
- For editorial changes:
102-
i. Open a PR with the changes to GOVERNANCE.md
103-
ii. Land the PR after getting at least two positive reviews, and waiting for at least 3 workdays across all time zones
104-
105-
_Note: PRs landed without SIPs can be challenged as substantial for up to 2 weeks afterwards, at which point they have to be backed out, and the proposed changes have to go through the SIP process instead._
89+
In the extreme case that objection-free consensus cannot be reached after a reasonable amount of time and effort, a committee member can call for a supermajority vote form the committee. If another member seconds the vote, the vote must take place.
10690

10791
## Glossary
10892

0 commit comments

Comments
 (0)