kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Grammatically updated Community Membership doc (#5479) 

* Grammatically updated Community Membership doc

* Update community-membership.md

Thanks Bob

Co-authored-by: Bob Killen <killen.bob@gmail.com>

* Update community-membership.md

Co-authored-by: Bob Killen <killen.bob@gmail.com>
This commit is contained in:
Mark Paget 2021-03-03 21:33:21 +08:00 committed by GitHub
parent a8bef09b45
commit dd629665a0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
community-membership.md
View File

@ -1,6 +1,6 @@
# Community membership
**Note:** This document is in progress
**Note:** This document is a work in progress
This doc outlines the various responsibilities of contributor roles in
Kubernetes. The Kubernetes project is subdivided into subprojects under SIGs.
@ -8,10 +8,10 @@ Responsibilities for most roles are scoped to these subprojects.
| Role | Responsibilities | Requirements | Defined by |
| -----| ---------------- | ------------ | -------|
| member | active contributor in the community | sponsored by 2 reviewers. multiple contributions to the project. | Kubernetes GitHub org member. |
| reviewer | review contributions from other members | history of review and authorship in a subproject | [OWNERS] file reviewer entry. |
| approver | approve accepting contributions | highly experienced and active reviewer + contributor to a subproject | [OWNERS] file approver entry|
| subproject owner | set direction and priorities for a subproject | demonstrated responsibility and excellent technical judgement for the subproject | [sigs.yaml] subproject [OWNERS] file *owners* entry |
| Member | Active contributor in the community | Sponsored by 2 reviewers and multiple contributions to the project | Kubernetes GitHub org member|
| Reviewer | Review contributions from other members | History of review and authorship in a subproject | [OWNERS] file reviewer entry |
| Approver | Contributions acceptance approval| Highly experienced active reviewer and contributor to a subproject | [OWNERS] file approver entry|
| Subproject owner | Set direction and priorities for a subproject | Demonstrated responsibility and excellent technical judgement for the subproject | [sigs.yaml] subproject [OWNERS] file *owners* entry |
## New contributors
@ -249,12 +249,12 @@ measured by the CNCF [DevStats project].
**Note:** Devstats does not take into account non-code contributions. If a
non-code contributing member is accidentally removed this way, they may open an
issue to quickly be re-instated.
issue to quickly be re-instated.
After an extended period away from the project with no activity
those members would need to re-familiarize themselves with the current state
before being able to contribute effectively.
before being able to contribute effectively.
[code reviews]: /contributors/guide/expectations.md#code-review