From 8885d2c75f11a3975098b033fed1d2374a5532ee Mon Sep 17 00:00:00 2001 From: Brendan Burns Date: Wed, 30 Jan 2019 12:24:28 -0800 Subject: [PATCH] Add a description of user groups. --- governance.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/governance.md b/governance.md index 6d4b6d7eb..71a2a965f 100644 --- a/governance.md +++ b/governance.md @@ -25,11 +25,12 @@ See [community membership] # Community groups -The project has 4 main types of groups: +The project has 5 main types of groups: * Special Interest Groups, SIGs * Subprojects * Working Groups, WGs * Committees +* User Groups ![Kubernetes Governance Diagram](kubernetes_governance_diagram.png) @@ -129,6 +130,21 @@ committee has a charter and a chair, and will report to the steering committee periodically, and to the community as makes sense, given the charter. +## User groups +Some topics have long term relevance to large groups of Kubernetes users, but +do not have clear deliverables or ownership of parts of the Kubernetes +code base. As such they are neither good fits for SIGs or Working Groups. +Examples of such a topic might be continuous delivery to Kubernetes. + +User groups function as a centralized resource to facilitate communication +and discovery of information related to the topic of the user group. User +groups should not undertake to produce any deliverable, instead they should +form working groups under the auspices of some SIG for such work. Likewise +they shouldn't take ownership of anything in the Kubernetes process, as +that is a role for SIGs. + +User groups are documented in [sigs.yaml](sigs.yaml) + ## Cross-project Communication and Coordination While most work shouldn’t require expensive coordination with other