diff options
| author | parispittman <parispittman@google.com> | 2020-04-06 10:51:42 -0700 |
|---|---|---|
| committer | parispittman <parispittman@google.com> | 2020-05-15 13:28:33 -0700 |
| commit | b801fe8f2c54001b776c54a91787326eae783194 (patch) | |
| tree | 59907e253db8d1296f0a4944594c62b05f09b634 /governance.md | |
| parent | b2c2f398a7360507c6e142b639692f390a63809c (diff) | |
adding community group health check
Diffstat (limited to 'governance.md')
| -rw-r--r-- | governance.md | 17 |
1 files changed, 14 insertions, 3 deletions
diff --git a/governance.md b/governance.md index 47668546..c08368c2 100644 --- a/governance.md +++ b/governance.md @@ -69,9 +69,9 @@ Each SIG must have a charter that specifies its scope (topics, subsystems, code repos and directories), responsibilities, areas of authority, how members and roles of authority/leadership are selected/granted, how decisions are made, and how conflicts are -resolved. See the [SIG charter process] for details on how charters are managed. -SIGs should be relatively free to customize or change how they operate, -within some broad guidelines and constraints imposed by cross-SIG processes +resolved. See the [SIG charter process] for details on how charters are managed. +SIGs should be relatively free to customize or change how they operate, +within some broad guidelines and constraints imposed by cross-SIG processes (e.g., the release process) and assets (e.g., the kubernetes repo). A primary reason that SIGs exist is as forums for collaboration. @@ -162,6 +162,15 @@ User Groups. To facilitate discoverability and engagement, user groups are documented in [sigs.yaml] +## Community Group Annual Reports +As you can see in the descriptions above, the project is robust with diverse +groups of contributors and their varying degrees of expected communications. + +The annual community group health check will establish an opportunity for deeper + dialogue and broader communication across the chairs of each group and the + Steering Committee. By including this reporting with the existing community + meeting structure, we can focus on the goals outlined in the [Annual Report] doc. + ## Cross-project Communication and Coordination While most work shouldn’t require expensive coordination with other @@ -214,4 +223,6 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md). [working group governance]: /committee-steering/governance/wg-governance.md [user group governance]: /committee-steering/governance/ug-governance.md [SIG Governance Requirements]: /committee-steering/governance/sig-governance-requirements.md +[Annual Report]: /committee-steering/governance/annual-reports.md +[monthly community meeting]: /events/community-meeting.md []() |