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
Copy file name to clipboardExpand all lines: GOVERNANCE.md
+3-19Lines changed: 3 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ The default decision making process is objection-free consensus. In other words
47
47
48
48
Decision making scenarios should be promoted appropriately by the maintainer overseeing the issue:
49
49
50
-
- tag maintainers in relevant issues / SIPs
50
+
- tag maintainers in relevant issues and SIPs
51
51
- send out mailing list reminders
52
52
- communicate updates in meetings
53
53
@@ -82,27 +82,11 @@ The Spin Governance Committee will select a chair to set agendas, call meetings,
82
82
83
83
### Decision Making
84
84
85
-
The default decision making process isobjection-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 isobjection-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.
86
86
87
87
Decision making scenarios should be promoted appropriately by the member overseeing the issue.
88
88
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.
0 commit comments