From 00b886bfbba2967f17e9792de7099565c6b50171 Mon Sep 17 00:00:00 2001 From: "James O. D. Hunt" Date: Tue, 16 Jan 2018 08:49:23 +0000 Subject: [PATCH 1/3] docs: Move developer info to Governance section in README Close reading shows that the Developer section should belong under the Governance section as the former discusses governance. Signed-off-by: James O. D. Hunt --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6c81fb30f6..356f85b765 100644 --- a/README.md +++ b/README.md @@ -5,10 +5,10 @@ * [Users](#users) * [Installing Clear Containers](#installing-clear-containers) * [Installing runV](#installing-runv) +* [Governance](#governance) * [Developers](#developers) * [Contributor](#contributor) * [Maintainer](#maintainer) -* [Governance](#governance) * [Architecture Committee](#architecture-committee) * [Working Committee](#working-committee) @@ -43,6 +43,10 @@ See https://github.com/clearcontainers/runtime/wiki/Installation. See https://github.com/hyperhq/runv. +# Governance + +The Kata Containers project is governed according to the [“four opens"](https://governance.openstack.org/tc/reference/opens.html), which are open source, open design, open development and open community. Technical decisions will be made by technical contributors and a representative Architecture Committee. The community is committed to diversity, openness, encouraging new contributors and leaders to rise up. + ## Developers For code contributors, there are currently two roles relevant to project governance: @@ -55,10 +59,6 @@ A Contributor to the Kata Containers project is someone who has merged code with A Maintainer has the ability to merge code into the Kata Containers project. Maintainers are active Contributors and participants in the projects. In order to become a Maintainer, you must be nominated and approved by the established Maintainers. Maintainers have write access to the Kata Containers repos on Github. -# Governance - -The Kata Containers project is governed according to the [“four opens"](https://governance.openstack.org/tc/reference/opens.html), which are open source, open design, open development and open community. Technical decisions will be made by technical contributors and a representative Architecture Committee. The community is committed to diversity, openness, encouraging new contributors and leaders to rise up. - ## Architecture Committee The Architecture Committee is responsible for architectural decisions, including standardization, and making final decisions if Maintainers disagree. It will be comprised of 5 members, who are appointed by the Maintainers at launch but fully elected by Contributors within the first year. The initial Architecture Committee members are Samual Ortiz, Xu Wang, Zhang Wei and Tim AllClair. From efa52e13eb8bd745dbb3cb2558c53d52200c1f90 Mon Sep 17 00:00:00 2001 From: "James O. D. Hunt" Date: Tue, 16 Jan 2018 08:51:48 +0000 Subject: [PATCH 2/3] docs: Add contributors section to README Added a new Contributors section that directs the reader to the contributing guide. Fixes #10. Signed-off-by: James O. D. Hunt --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 356f85b765..ae74842189 100644 --- a/README.md +++ b/README.md @@ -5,6 +5,7 @@ * [Users](#users) * [Installing Clear Containers](#installing-clear-containers) * [Installing runV](#installing-runv) + * [Contributors](#contributors) * [Governance](#governance) * [Developers](#developers) * [Contributor](#contributor) @@ -43,6 +44,10 @@ See https://github.com/clearcontainers/runtime/wiki/Installation. See https://github.com/hyperhq/runv. +## Contributors + +See the [contributing guide](CONTRIBUTING.md) for details on how to contribute to the project. + # Governance The Kata Containers project is governed according to the [“four opens"](https://governance.openstack.org/tc/reference/opens.html), which are open source, open design, open development and open community. Technical decisions will be made by technical contributors and a representative Architecture Committee. The community is committed to diversity, openness, encouraging new contributors and leaders to rise up. @@ -53,7 +58,7 @@ For code contributors, there are currently two roles relevant to project governa ### Contributor -A Contributor to the Kata Containers project is someone who has merged code within the last 12 months. Contributors are eligible to vote in the Architecture Committee elections. Contributors have read only access to the Kata Containers repos on Github. +A Contributor to the Kata Containers project is someone who has had code merged within the last 12 months. Contributors are eligible to vote in the Architecture Committee elections. Contributors have read only access to the Kata Containers repos on Github. ### Maintainer From 9ab510d417f471fea65b8a736362ab5806d2cdaa Mon Sep 17 00:00:00 2001 From: "James O. D. Hunt" Date: Thu, 18 Jan 2018 09:40:50 +0000 Subject: [PATCH 3/3] docs: Use Oxford Comma in Governance wording Based on review feedback, updated the Governance section slightly to use an Oxford Comma before the last list item. Signed-off-by: James O. D. Hunt --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ae74842189..ec92ac1650 100644 --- a/README.md +++ b/README.md @@ -50,7 +50,7 @@ See the [contributing guide](CONTRIBUTING.md) for details on how to contribute t # Governance -The Kata Containers project is governed according to the [“four opens"](https://governance.openstack.org/tc/reference/opens.html), which are open source, open design, open development and open community. Technical decisions will be made by technical contributors and a representative Architecture Committee. The community is committed to diversity, openness, encouraging new contributors and leaders to rise up. +The Kata Containers project is governed according to the [“four opens"](https://governance.openstack.org/tc/reference/opens.html), which are open source, open design, open development, and open community. Technical decisions are made by technical contributors and a representative Architecture Committee. The community is committed to diversity, openness, and encouraging new contributors and leaders to rise up. ## Developers