Add initial governance structure

proposals/0024/GOVERNANCE.md

@@ -0,0 +1,33 @@
+# 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<sup>[1],[2]</sup> 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<sup>[3]</sup>.
+
+## 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"<sup>[4]</sup>.
+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
+- amount and consistency of contributions and activity
+
+| Role        | Responsibilities | Requirements | Defined by |
+| -----       | ---------------- | ------------ | ------- |
+| 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
+

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)