summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNikhita Raghunath <nikitaraghunath@gmail.com>2019-02-27 07:59:07 +0530
committerNikhita Raghunath <nikitaraghunath@gmail.com>2019-03-05 00:31:30 +0530
commitb7e7ae9f5bcb108ff37fdfce5154137cb9702c15 (patch)
treee7257f19c9f439358f897bc2f6d690d066879526
parent44c77b522097fd069a6669fa08b81ec9ebf5e836 (diff)
governance: s/working groups/user groups in user groups description
-rw-r--r--governance.md4
1 files changed, 2 insertions, 2 deletions
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