From 95812ba687e90924d978655a42bab25783d86f2a Mon Sep 17 00:00:00 2001 From: Jacob Weinstock Date: Wed, 21 Jul 2021 10:24:10 -0600 Subject: [PATCH 1/2] Add initial governance structure Signed-off-by: Jacob Weinstock --- proposals/0024/GOVERNANCE.md | 30 ++++++++++++++++++++++++++++++ proposals/0024/README.md | 24 ++++++++++++++++++++++++ 2 files changed, 54 insertions(+) create mode 100644 proposals/0024/GOVERNANCE.md create mode 100644 proposals/0024/README.md diff --git a/proposals/0024/GOVERNANCE.md b/proposals/0024/GOVERNANCE.md new file mode 100644 index 0000000..63cc75a --- /dev/null +++ b/proposals/0024/GOVERNANCE.md @@ -0,0 +1,30 @@ +# Governance + +This document describes how the Liberal contribution governance structure is implemented in the Tinkerbell community. + +## What is Liberal contribution? + +Under a liberal contribution model, the people who do the most work [in the prescribed way] are recognized as most influential, but this is based on current work and not historic contributions. +Major project decisions are made based on a consensus seeking process (discuss major grievances) rather than pure vote, and strive to include as many community perspectives as possible. +Popular examples of projects that use a liberal contribution model include Node.js and Rust [1]. + +## Community Roles + +This doc outlines the various roles in the Tinkerbell community. + +One of the overarching goals of having different roles in the community is to make sure to "allow good changes to enter the code with a minimum of fuss"[2]. +The following criteria is to be used when considering and individual for a role. + +- a pattern of good judgement in regard to the code bases and to oneself +- demonstrated history of "playing nice" in the community +- amount and consistency of contributions and activity + +| Role | Responsibilities | Requirements | Defined by | +| ----- | ---------------- | ------------ | ------- | +| Contributor | Submit contributions | signed DCO | n/a | +| Member | issue and discussion administration, PR approval | history of activity, good judgement, and contribution in the community and the repositories, Sponsored by 2 Committers | Tinkerbell GitHub org member | +| Committer | Right to make changes to the code bases | same as Member and shows leadership in the community and the repositories, sponsored by 2 Maintainers | [OWNERS] file reviewer entry | +| Maintainer | Voting privileges | same as Committer, voted in by existing Maintainers | [OWNERS] file reviewer entry | + +[1]: https://opensource.guide/leadership-and-governance/#what-are-some-of-the-common-governance-structures-for-open-source-projects +[2]: https://producingoss.com/html-chunk/committers.html diff --git a/proposals/0024/README.md b/proposals/0024/README.md new file mode 100644 index 0000000..04df213 --- /dev/null +++ b/proposals/0024/README.md @@ -0,0 +1,24 @@ +--- +id: 0024 +title: Community Membership +status: ideation +authors: Jacob Weinstock +--- + +## Summary + +This proposal is to define a document outlining community governance and roles. + +## Goals and not Goals + +Goals: + +- get something defined for governance and roles + +No-Goal: + +- a comprehensive document of governance and roles + +## Content + +[goverannce](GOVER.md) From 5917ee2c1bb772c6fa8a6697d33383b606e98e4a Mon Sep 17 00:00:00 2001 From: Jacob Weinstock Date: Thu, 12 Aug 2021 14:59:58 -0600 Subject: [PATCH 2/2] updates Signed-off-by: Jacob Weinstock --- proposals/0024/GOVERNANCE.md | 23 +++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/proposals/0024/GOVERNANCE.md b/proposals/0024/GOVERNANCE.md index 63cc75a..830f648 100644 --- a/proposals/0024/GOVERNANCE.md +++ b/proposals/0024/GOVERNANCE.md @@ -5,15 +5,15 @@ This document describes how the Liberal contribution governance structure is imp ## What is Liberal contribution? Under a liberal contribution model, the people who do the most work [in the prescribed way] are recognized as most influential, but this is based on current work and not historic contributions. -Major project decisions are made based on a consensus seeking process (discuss major grievances) rather than pure vote, and strive to include as many community perspectives as possible. -Popular examples of projects that use a liberal contribution model include Node.js and Rust [1]. +Major project decisions are made based on a consensus seeking[1],[2] process (discuss major grievances) rather than pure vote, and strive to include as many community perspectives as possible. +Popular examples of projects that use a liberal contribution model include Node.js and Rust[3]. ## Community Roles This doc outlines the various roles in the Tinkerbell community. -One of the overarching goals of having different roles in the community is to make sure to "allow good changes to enter the code with a minimum of fuss"[2]. -The following criteria is to be used when considering and individual for a role. +One of the overarching goals of having different roles in the community is to make sure to "allow good changes to enter the code with a minimum of fuss"[4]. +The following criteria is to be used when considering an individual for a role. - a pattern of good judgement in regard to the code bases and to oneself - demonstrated history of "playing nice" in the community @@ -21,10 +21,13 @@ The following criteria is to be used when considering and individual for a role. | Role | Responsibilities | Requirements | Defined by | | ----- | ---------------- | ------------ | ------- | -| Contributor | Submit contributions | signed DCO | n/a | -| Member | issue and discussion administration, PR approval | history of activity, good judgement, and contribution in the community and the repositories, Sponsored by 2 Committers | Tinkerbell GitHub org member | -| Committer | Right to make changes to the code bases | same as Member and shows leadership in the community and the repositories, sponsored by 2 Maintainers | [OWNERS] file reviewer entry | -| Maintainer | Voting privileges | same as Committer, voted in by existing Maintainers | [OWNERS] file reviewer entry | +| Contributor | Submit contributions | Signed DCO | Registered GitHub User | +| Member | Issue and discussion administration, PR reviewer | History of activity, good judgement, contribution in the community and the repositories, and sponsored by 2 Committers | Tinkerbell GitHub org member | +| Committer | Right to make changes to the code bases, merge pull requests, etc | Same as Member, shows leadership in the community and the repositories, and sponsored by 2 Maintainers | [OWNERS] file committer entry | +| Maintainer | Voting privileges, set direction and priorities | Same as Committer, demonstrated responsibility and excellent technical judgement for the project, and voted in by existing Maintainers | [OWNERS] file maintainer entry | + +[1]: https://producingoss.com/html-chunk/consensus-democracy.html +[2]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making +[3]: https://opensource.guide/leadership-and-governance/#what-are-some-of-the-common-governance-structures-for-open-source-projects +[4]: https://producingoss.com/html-chunk/committers.html -[1]: https://opensource.guide/leadership-and-governance/#what-are-some-of-the-common-governance-structures-for-open-source-projects -[2]: https://producingoss.com/html-chunk/committers.html