Add User Group governance
This commit is contained in:
dsatya
parent
2308ac96a8
commit
c822f15ada
|
|
@ -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
|
||||
|
|
@ -159,6 +159,9 @@ shouldn't take ownership of anything in the Kubernetes process, as that is a
|
|||
role for SIGs. All user group chairs, and others that hold leadership positions
|
||||
within a user group must be [community members].
|
||||
|
||||
See [user group governance] for more details about forming and disbanding
|
||||
User Groups.
|
||||
|
||||
To facilitate discoverability and engagement,
|
||||
user groups are documented in [sigs.yaml]
|
||||
|
||||
|
|
@ -213,5 +216,6 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md).
|
|||
[short template]: /committee-steering/governance/sig-governance-template-short.md
|
||||
[kubernetes repository guidelines]: /github-management/kubernetes-repositories.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
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
## SUMMARY:
|
||||
|
||||
This document covers everything you need to know about the creation and retirement (“lifecycle”) of a special interest or working group within the Kubernetes project. General project governance information can be found in the [steering committee repo].
|
||||
This document covers everything you need to know about the creation and retirement (“lifecycle”) of a special interest, working group or user group within the Kubernetes project. General project governance information can be found in the [steering committee repo].
|
||||
Out of scope for this document: [subproject] creation.
|
||||
|
||||
[Creation]
|
||||
|
|
@ -19,13 +19,27 @@ Out of scope for this document: [subproject] creation.
|
|||
- [ ] Read [wg-governance.md]
|
||||
- [ ] Ensure all WG Organizers, and other leadership roles are [community members]
|
||||
- [ ] Send email to [kubernetes-dev@googlegroups.com] titled "WG-Creation-Request: WG Foo" with some of the questions answered from wg-goverance.md and wait for community discourse; ask for SIG sponsorship
|
||||
- [ ] Do the first checklist item in the #GitHub section below and add a row to the WG section:
|
||||
- [ ] Do the first checklist item in the [GitHub] section below and add a row to the WG section:
|
||||
- [ ] Label with committee/steering and wait for a simple majority
|
||||
- [ ] Also add sponsoring SIG Chair/Tech Leads as approvers; you'll get this from the community email above
|
||||
- [ ] Place a `/hold` on it until the members that need to review have; a contributor experience member will do this for you if they don't see one already
|
||||
- [ ] Send an email to the stakeholder SIG mailing lists and steering committee with the sigs.yaml pull request
|
||||
|
||||
### GitHub:
|
||||
### Prerequisites for a UG
|
||||
- [ ] Read [ug-governance.md]
|
||||
- [ ] Require to have 2 Chairs to start a User Group.
|
||||
- [ ] Require to have at least 2 members other than chairs to be a part of the User Group.
|
||||
- [ ] Requires at least 2 sponsors from steering or lazy consensus (In case of no objection within 7 week days).
|
||||
- [ ] Send an email to kubernetes-dev@googlegroups.com and steering@kubernetes.io titled "UG-Creation-Request: UG Foo" answering the following questions and wait for community discourse:
|
||||
- [ ] What topics are in scope for this user group?
|
||||
- [ ] What is the meeting cadence?
|
||||
- [ ] Who will chair the group, and ensure it continues to meet the requirements?
|
||||
- [ ] Do the first checklist item in the [GitHub] section below and add a row to the UG section:
|
||||
- [ ] Label with committee/steering and place a `/hold` on it.
|
||||
- [ ] Send an email to the steering committee with the [sigs.yaml] pull request.
|
||||
|
||||
|
||||
### [GitHub]
|
||||
- [ ] Submit a PR that will add rows to [sigs.yaml] using the [generator doc]; this will create README files and OWNERS_ALIASES files for your new directory in `kubernetes/community`
|
||||
- You’ll need:
|
||||
- SIG Name
|
||||
|
|
@ -44,7 +58,7 @@ Each one of these has a linked canonical source guideline from set up to moderat
|
|||
- [ ] Read [moderation.md] and understand your role in keeping our community safe
|
||||
- [ ] Create your mailing lists - One for your members and another for your chairs/leads
|
||||
- Either [GoogleGroups] OR [discuss.kubernetes.io]
|
||||
- Example: kubernetes-[sig/wg]-foo@googlegroups.com and kubernetes-[sig/wg]-foo-leads@googlegroups.com
|
||||
- Example: kubernetes-[sig/wg/ug]-foo@googlegroups.com and kubernetes-[sig/wg/ug]-foo-leads@googlegroups.com
|
||||
- The chairs/leads email will be used for activation of certain platforms (eg zoom)
|
||||
- [ ] Request a slack channel. [slack-guidelines.md]
|
||||
- [ ] Request a YouTube playlist link [youtube-guidelines.md]
|
||||
|
|
@ -70,14 +84,19 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
|
|||
### Prerequisites for WG Retirement
|
||||
- [ ] Have completed the mission of the WG or have another reason as outlined in [wg-governance.md]
|
||||
|
||||
### Prerequisites for UG Retirement
|
||||
- [ ] There is no longer a chair and no one is nominated within the 4-week grace period.
|
||||
- [ ] There has been no meeting conducted by the chair in 8 weeks.
|
||||
- [ ] There is no activity on communication channels.
|
||||
|
||||
### Steps:
|
||||
- [ ] Send an email to kubernetes-dev@googlegroups.com and community@kubernetes.io alerting the community of your intentions to disband or merge. [example]
|
||||
- This kicks off the process for Contributor Experience’s community managers who will reach out and set an issue against `kubernetes/community` with exact next steps covered below. We can help walk through this when you get there. Most of this is covered in the same creation communication docs as above.
|
||||
- [ ] Archive the member and lead/chair mailing lists/[GoogleGroups]
|
||||
- [ ] Check the [slack-guidelines.md] for latest process on archiving the slack channel
|
||||
- [ ] Deactivate the zoom license
|
||||
- [ ] Delete your shared SIG/WG calendar
|
||||
- [ ] Ensure that the [youtube-guidelines.md] links are removed and you've uploaded all SIG/WG meetings to date
|
||||
- [ ] Delete your shared SIG/WG/UG calendar
|
||||
- [ ] Ensure that the [youtube-guidelines.md] links are removed and you've uploaded all SIG/WG/UG meetings to date
|
||||
- [ ] Move the existing SIG directory into the archive in `kubernetes/community`
|
||||
- [ ] GitHub archiving/removing/other transactions:
|
||||
- [ ] Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org
|
||||
|
|
@ -94,6 +113,7 @@ Sometimes it might be necessary to sunset a SIG or Working Group. SIGs/WGs may a
|
|||
[subproject]: /governance.md#subprojects
|
||||
[Creation]: #Creation
|
||||
[Retirement]: #Retirement
|
||||
[GitHub]: #GitHub
|
||||
[sig-governance.md]: /committee-steering/governance/sig-governance.md
|
||||
[SIG charter process]: /committee-steering/governance
|
||||
[wg-governance.md]: /committee-steering/governance/wg-governance.md
|
||||
|
|
|
|||
Loading…
Reference in New Issue