github/kata-containers
1
0
Fork 1
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-08-19 08:28:19 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #11 from jodh-intel/ref-contrib-doc

Browse Source 
Move Developer section and reference the contributing guide
This commit is contained in:
James O. D. Hunt 2018-01-19 07:54:30 +00:00 committed by GitHub
commit d83ea6cf41
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
README.md
View File

@ -5,10 +5,11 @@
* [Users](#users) * [Users](#users)
* [Installing Clear Containers](#installing-clear-containers) * [Installing Clear Containers](#installing-clear-containers)
* [Installing runV](#installing-runv) * [Installing runV](#installing-runv)
* [Contributors](#contributors)
* [Governance](#governance)
* [Developers](#developers) * [Developers](#developers)
* [Contributor](#contributor) * [Contributor](#contributor)
* [Maintainer](#maintainer) * [Maintainer](#maintainer)
* [Governance](#governance)
* [Architecture Committee](#architecture-committee) * [Architecture Committee](#architecture-committee)
* [Working Committee](#working-committee) * [Working Committee](#working-committee)
@ -43,22 +44,26 @@ See https://github.com/clearcontainers/runtime/wiki/Installation.
See https://github.com/hyperhq/runv. 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 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 ## Developers
For code contributors, there are currently two roles relevant to project governance: For code contributors, there are currently two roles relevant to project governance:
### Contributor ### 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 ### Maintainer
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. 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 ## 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. 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.