diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-03-04 11:35:52 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-03-04 11:35:52 -0800 |
| commit | 44e02e054b25af52b02bb17c87ea896e5fdb6a29 (patch) | |
| tree | d26a898bf5a48d8192c9b5b4d667f506b4551ff0 | |
| parent | b1b7c92cbac53cc81a85d8a2dfdf40e471a23687 (diff) | |
| parent | b7e7ae9f5bcb108ff37fdfce5154137cb9702c15 (diff) | |
Merge pull request #3299 from nikhita/user-groups-readme
Add User Groups to README
| -rw-r--r-- | README.md | 5 | ||||
| -rw-r--r-- | governance.md | 4 |
2 files changed, 6 insertions, 3 deletions
@@ -15,7 +15,7 @@ For more specific topics, try a SIG. ## Governance -Kubernetes has three types of groups that are officially supported: +Kubernetes has the following types of groups that are officially supported: * **Committees** are named sets of people that are chartered to take on sensitive topics. This group is encouraged to be as open as possible while achieving its mission but, because of the nature of the topics discussed, private communications are allowed. @@ -30,6 +30,9 @@ Kubernetes has three types of groups that are officially supported: * **Working Groups** are temporary groups that are formed to address issues that cross SIG boundaries. Working groups do not own any code or other long term artifacts. Working groups can report back and act through involved SIGs. +* **User Groups** are groups for facilitating communication and discovery of information related to + topics that have long term relevance to large groups of Kubernetes users. + They do not have ownership of parts of the Kubernetes code base. See the [full governance doc](governance.md) for more details on these groups. diff --git a/governance.md b/governance.md index 7cdee4cb..8dfc32cc 100644 --- a/governance.md +++ b/governance.md @@ -137,13 +137,13 @@ code base. As such they are neither good fits for SIGs or Working Groups. An example of such a topic might be continuous delivery to Kubernetes. Though their central goal is not a a deliverable piece of work, as contributing -members of the community working groups are expected to work with SIGs +members of the community user groups are expected to work with SIGs to either identify friction or usability issues that need to be addressed, or to provide or improve documentation in their area of expertise. However these activities are covered under general code contributions to the relevant SIGs (e.g. SIG Docs) rather than as part of the user group. These contributions are expected to be more incremental and ad-hoc versus the more targeted -output of a working group. +output of a user group. User groups function as a centralized resource to facilitate communication and discovery of information related to the topic of the user group. User |