Merge pull request #3620 from daminisatya/UG_Governance

Add User Group governance

1 files changed, 39 insertions, 0 deletions

diff --git a/committee-steering/governance/ug-governance.md b/committee-steering/governance/ug-governance.md
new file mode 100644
index 00000000..400179b2
--- /dev/null
+++ b/committee-steering/governance/ug-governance.md
@@ -0,0 +1,39 @@
+# Kubernetes User Group (UG)
+
+## Introduction
+The Kubernetes community and ecosystem benefits providing a place for communication and collaboration between users and community members on topics that either do not have deliverables or are outside the scope of the project itself. These topics are not appropriate for forming SIGs, WGs or Committees, which are intended to drive work within the project. User Groups are the venue for this kind of communication and collaboration.
+
+Example User Groups:
+
+- Big Data - Topics related to Big Data integrations.
+- Cloud Providers - Topics related to public/private cloud provider integrations.
+- Machine Learning - Topics related to ML ecosystem integrations.
+- DevOps - Topics related to DevOps tools and deployments.
+
+## UG Goals
+- Facilitate communication between Kubernetes users and contributors on topics pertaining to - the usage of, the extension of and integration with Kubernetes and Kubernetes subprojects.
+
+## UG Anti-Goals
+- Producing or owning Kubernetes project deliverables or assets.
+- Making Kubernetes project decisions.
+- Creating Kubernetes project roles.
+- Claiming ownership of any specific topic.
+
+## UG Example Activities
+- Facilitating collaboration between user group members - which may result in the production of - blogs, docs, guides, demos, presentations, prototypes, external contributions, etc. (UG is itself not responsible to create any such content, it merely facilitate members creating them).
+- Anything produced within the context of the user group can be ultimately owned by a SIG as a subproject or is owned by individuals in the user group.
+- Publishing content such as FAQs, READMEs, or other forms of documentation to a GitHub directory owned by the user group. Access to this location is controlled by OWNERS files. OWNERS files are seeded at user group creation time with the Chairs.
+- Providing updates from the user group’s activities to the community at large.
+  - Cadence - every release.
+  - Improvements/Contributions/Pain-points through the user group to the ecosystem (features enabled, user group specific engagements, etc.)
+
+## Assets Owned by UG
+- Calendar Events
+- Slack Channel
+- Discussion Forum Groups
+- GitHub Directory
+
+## Creation and Disbandment of UG
+The process for setting up a User Group (UG) is listed in the [sig-wg-lifecycle] document.
+
+[sig-wg-lifecycle]: /sig-wg-lifecycle.md