kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7407 from cantbewong/retirevmwareug 

Retire VMware User Group and remove User Groups as a K8s Group category since this removes the last, only one
This commit is contained in:
Kubernetes Prow Robot 2023-07-27 17:29:52 -07:00 committed by GitHub
parent 2ecc29b85d d295c309d0
commit 39cae63d5f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
21 changed files with 26 additions and 241 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
OWNERS_ALIASES
View File

@ -144,11 +144,6 @@ aliases:
wg-structured-logging-leads:
- pohly
- serathius
ug-vmware-users-leads:
- brysonshepherd
- cantbewong
- mylesagray
- phenixblue
committee-code-of-conduct:
- detiber
- endocrimes

3
README.md
View File

@ -30,9 +30,6 @@ Kubernetes has the following types of groups that are officially supported:
* **Working Groups** are temporary groups that are formed to address issues that cross SIG boundaries.
Working groups do not own any code or other long term artifacts.
Working groups can report back and act through involved SIGs.
* **User Groups** are groups for facilitating communication and discovery of information related to
topics that have long term relevance to large groups of Kubernetes users.
They do not have ownership of parts of the Kubernetes code base.
See the [full governance doc](governance.md) for more details on these groups.

0
ug-vmware-users/README.md → archive/ug-vmware-users/README.md
View File

10
committee-steering/governance/annual-reports.md
View File

@ -1,15 +1,14 @@
# Kubernetes Community Group Annual Reports
This document outlines the process for an annual reporting and
communication structure for Special Interest Groups (SIGs), Working Groups (WGs),
User Groups (UGs), and Committees.
All policy updates will be in their respective [SIG], [WG], and [UG]
communication structure for Special Interest Groups (SIGs), Working Groups (WGs), and Committees.
All policy updates will be in their respective [SIG] or [WG]
governance docs as well as the general [governance] guidance.
## Goals
- Paint a complete project health picture for all of our community groups
- Create a feedback loop between Chairs, Tech Leads, Subproject Owners, WG and
UG Organizers, the community groups at large, and the Steering
- Create a feedback loop between Chairs, Tech Leads, Subproject Owners, WG
Organizers, the community groups at large, and the Steering
Committee to move the project forward
- Encourage dialogue about the wellbeing of the projects contributors and offer
suggested guidance and coaching
@ -289,6 +288,5 @@ https://www.apache.org/foundation/board/reporting
[SIG]: https://git.k8s.io/community/committee-steering/governance/sig-governance.md
[WG]: https://git.k8s.io/community/committee-steering/governance/wg-governance.md
[UG]: https://git.k8s.io/community/committee-steering/governance/ug-governance.md
[governance]: https://git.k8s.io/community/governance.md
[questions]: #questions-for-report

44
committee-steering/governance/ug-governance.md
View File

@ -1,44 +0,0 @@
# 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 Activities
- Present yearly [group health check] to Steering Committee
## 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
[group health check]: ./annual-reports.md

2
communication/calendar-guidelines.md
View File

@ -115,8 +115,6 @@ In case you are creating a calendar event and wondering what to include in it, h
[SIG-<name>] <meeting title>
or
[WG-<name>] <meeting title>
or
[User Group-<name>]
```
#### Description

6
communication/slack-guidelines.md
View File

@ -150,7 +150,7 @@ To add a channel, open a Pull Request (PR) updating the [slack-config].
- `#projectname`
- In the PR comments, include some details regarding the purpose of the
Channel.
- Channels should be dedicated to [SIGs, WGs, UGs][sig-list], sub-projects,
- Channels should be dedicated to [SIGs or WGs][sig-list], sub-projects,
community topics, or related Kubernetes programs/projects.
- Linking to resources such as the PR adding the subproject will speed in
the validation and processing of the channel creation request.
@ -299,7 +299,7 @@ bots, tokens or webhooks. Please see the processes outlined below.
#### Processing Channel Requests
Channel requests should be reviewed for their relation and relevance to the
Kubernetes community. Typically channels should be dedicated to SIGs, WGs, UGs,
Kubernetes community. Typically channels should be dedicated to SIGs, WGs,
sub-projects, community topics, and other things related to Kubernetes programs
and projects.
@ -307,7 +307,7 @@ For Kubernetes project centric requests, validate them against the
[sig-list], or request a link to a related issue/PR, or mailing
list discussion for the requested Channel.
Small external projects are encouraged to use the channel of the SIG, WG, or UG
Small external projects are encouraged to use the channel of the SIG or WG
most relevant to them. Other things such as programming language-specific
channels are discouraged and should in turn be steered to `#kubernetes-client`
or communication avenues commonly used by their specific language.

4
communication/youtube/youtube-guidelines.md
View File

@ -21,11 +21,11 @@ and includes all communications such as YouTube.
## Meeting Playlists
The [Kubernetes YouTube Channel] has separate playlists for each SIG, WG, UG
The [Kubernetes YouTube Channel] has separate playlists for each SIG or WG
meeting recordings, as well as recordings of other recurring events such as the
Kubernetes [community meeting], and others.
[Subprojects], in addition to SIGs, WGs, UGs may request their own playlists
[Subprojects], in addition to SIGs and WGs may request their own playlists
to better target their contributors and increase general discoverability.
To better serve the community, [collaboration] has been enabled to share the

4
contributors/guide/style-guide.md
View File

@ -104,7 +104,7 @@ These are **guidelines**, not rules. Use your best judgement.
- If using acronyms, ensure they are clearly defined in the same document.
- If using an abbreviation, spell it out the first time it is used in the
document unless it is commonly known. (example: TCP/IP)
- When referring to a Kubernetes Group (SIG, WG, or UG) do not use the hyphenated
- When referring to a Kubernetes Group (SIG or WG) do not use the hyphenated
form unless it is for a specific purpose such as a file-name or URI.
**[Moving a Document:](#moving-a-document)**
@ -393,7 +393,7 @@ external appearance.
- **Good example:** A _CustomResourceDefinition_ (CRD) extends the Kubernetes
API.
- **Bad example:** A CRD extends the Kubernetes API.
- When referring to a Kubernetes Group (SIG, WG, or UG) do not use the hyphenated
- When referring to a Kubernetes Group (SIG or WG) do not use the hyphenated
form unless it is for a specific purpose such as a file-name or URI.
- **Good example:** SIG Docs oversees the Kubernetes website.
- **Bad example:** SIG-Docs oversees the Kubernetes website.

2
elections/steering/documentation/template/README.md
View File

@ -107,7 +107,7 @@ Committee's governance will be considered for voter exception.
Examples of contributions that would be considered:
* Slack admins who are not active in GitHub
* K8s Infra staff doing mostly support
* Working Group or User Group leads without a lot of GitHub activity
* Working Group leads without a lot of GitHub activity
Examples of contributions that would NOT be considered:
* Contributions to ecosystem projects and products

4
elections/teams/README.md
View File

@ -5,8 +5,8 @@ we can host any number of elections for community groups, as they need them.
## Who Can Request an Election
Any "Kubernetes team" can request an election. This includes SIGs, Working Groups,
User Groups, operational teams like Release Engineering or Enhancements,
Any "Kubernetes team" can request an election. This includes SIGs, Working
Groups, operational teams like Release Engineering or Enhancements,
Subprojects, and even wholly subsidiary projects like Prow and ClusterAPI.
Basically, if your group is all Kubernetes contributors, you can ask for an
election.

8
generator/README.md
View File

@ -1,8 +1,8 @@
# SIG Doc builder
This folder contains scripts to automatically generate documentation about the
different Special Interest Groups (SIGs), Working Groups (WGs),
User Groups (UGs) and Committees of Kubernetes. The authoritative
different Special Interest Groups (SIGs), Working Groups (WGs)
and Committees of Kubernetes. The authoritative
source for SIG information is the [`sigs.yaml`](/sigs.yaml) file in the project root.
All updates must be done there.
@ -14,7 +14,6 @@ The documentation follows a template and uses the values from [`sigs.yaml`](/sig
- List: [`list.tmpl`](list.tmpl)
- SIG README: [`sig_readme.tmpl`](sig_readme.tmpl)
- WG README: [`wg_readme.tmpl`](wg_readme.tmpl)
- UG README: [`ug_readme.tmpl`](ug_readme.tmpl)
- Committee README: [`committee_readme.tmpl`](committee_readme.tmpl)
**Time Zone gotcha**:
@ -31,7 +30,6 @@ accompanying documentation. This takes the format of the following types of doc
```
sig-<sig-name>/README.md
wg-<working-group-name>/README.md
ug-<user-group-name>/README.md
committee-<committee-name>/README.md
sig-list.md
```
@ -91,7 +89,7 @@ for i in $(ls -1 generator/generated/*.md); do hub issue create -F $i && rm $i;
### README
If your SIG, WG, UG or Committee wishes to add custom content, you can do so by placing it within
If your SIG, WG or Committee wishes to add custom content, you can do so by placing it within
the following code comments:
```markdown

2
generator/liaisons.tmpl
View File

@ -18,7 +18,7 @@ the Steering Committee.
Liaisons are assigned community groups at random (adjustments can be
made, if needed) with each member having an (almost) equal distribution
of SIGs, WGs and UGs. Each year after Steering Committee elections, new
of SIGs and WGs. Each year after Steering Committee elections, new
members will assume one of the departing members groups.
| Community Group | Steering Committee Liaison |

10
generator/list.tmpl
View File

@ -2,7 +2,7 @@
title: Community Groups
linkTitle: Community Groups
description: |
A list of our community groups: Special Interest Groups, Working Groups, User Groups and Committees.
A list of our community groups: Special Interest Groups, Working Groups and Committees.
weight: 99
type: docs
aliases: [ "/groups", "/sigs" ]
@ -45,14 +45,6 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[{{.Name}}]({{.Dir}}/README.md)|[{{.Label}}](https://github.com/kubernetes/kubernetes/labels/wg%2F{{.Label}})|{{range .StakeholderSIGs}}* {{.}}<br>{{end }}|{{range .Leadership.Chairs}}* [{{.Name}}](https://github.com/{{.GitHub}}){{if .Company}}, {{.Company}}{{end}}<br>{{end}}|* [Slack](https://kubernetes.slack.com/messages/{{.Contact.Slack}})<br>* [Mailing List]({{.Contact.MailingList}})|{{range .Meetings}}* {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}} ({{.Frequency}})]({{.URL}})<br>{{end}}
{{- end }}
### User Groups
| Name | Label |Organizers | Contact | Meetings |
|------|-------|------------|--------|----------|
{{- range .UserGroups}}
|[{{.Name}}]({{.Dir}}/README.md)|[{{.Label}}](https://github.com/kubernetes/kubernetes/labels/ug%2F{{.Label}})|{{range .Leadership.Chairs}}* [{{.Name}}](https://github.com/{{.GitHub}}){{if .Company}}, {{.Company}}{{end}}<br>{{end}}|* [Slack](https://kubernetes.slack.com/messages/{{.Contact.Slack}})<br>* [Mailing List]({{.Contact.MailingList}})|{{range .Meetings}}* {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}} ({{.Frequency}})]({{.URL}})<br>{{end}}
{{- end }}
### Committees
| Name | Label | Members | Contact |

57
generator/ug_readme.tmpl
View File

@ -1,57 +0,0 @@
{{- template "header" }}
# {{.Name}} User Group
{{ .MissionStatement }}
{{- if .CharterLink }}
The [charter]({{.CharterLink}}) defines the scope and governance of the {{.Name}} User Group.
{{ end }}
{{ if .Meetings -}}
## Meetings
{{- if .Contact.MailingList }}
*Joining the [mailing list]({{.Contact.MailingList}}) for the group will typically add invites for the following meetings to your calendar.*
{{- end }}
{{- range .Meetings }}
* {{.Description}}: [{{.Day}}s at {{.Time}} {{.TZ}}]({{.URL}}) ({{.Frequency}}). [Convert to your timezone](http://www.thetimezoneconverter.com/?t={{.Time}}&tz={{.TZ | tzUrlEncode}}).
{{- if .ArchiveURL }}
* [Meeting notes and Agenda]({{.ArchiveURL}}).
{{- end }}
{{- if .RecordingsURL }}
* [Meeting recordings]({{.RecordingsURL}}).
{{- end }}
{{- end }}
{{- end }}
{{- if .Leadership }}
{{- if .Leadership.Chairs }}
## Organizers
{{ range .Leadership.Chairs }}
* {{.Name}} (**[@{{.GitHub}}](https://github.com/{{.GitHub}})**){{if .Company}}, {{.Company}}{{end}}
{{- end }}
{{- end }}
{{- if .Leadership.EmeritusLeads }}
## Emeritus Organizers
{{ range .Leadership.EmeritusLeads }}
* {{.Name}} (**[@{{.GitHub}}](https://github.com/{{.GitHub}})**)
{{- end }}
{{- end }}
{{- end }}
## Contact
- Slack: [#{{.Contact.Slack}}](https://kubernetes.slack.com/messages/{{.Contact.Slack}})
- [Mailing list]({{.Contact.MailingList}})
{{- if .Label }}
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/ug%2F{{.Label}})
{{- end }}
{{- if .Contact.GithubTeams }}
- GitHub Teams:
{{- range .Contact.GithubTeams }}
- [@kubernetes/{{.Name}}](https://github.com/orgs/kubernetes/teams/{{.Name}}) {{- if .Description }} - {{.Description}} {{- end}}
{{- end }}
{{- end }}
{{- if .Contact.Liaison.Name }}
- Steering Committee Liaison: {{.Contact.Liaison.Name}} (**[@{{.Contact.Liaison.GitHub}}](https://github.com/{{.Contact.Liaison.GitHub}})**)
{{- end }}

31
governance.md
View File

@ -34,7 +34,6 @@ The project is comprised of the following types of subgroups:
* Subprojects
* Working Groups, WGs
* Committees
* User Groups
![Kubernetes Governance Diagram](kubernetes_governance_diagram.png)
@ -133,35 +132,6 @@ however, all committee members must be [community members]. Like a SIG, a
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.
An example of such a topic might be continuous delivery to Kubernetes.
Though their central goal is not a deliverable piece of work, as contributing
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 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 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. 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].
## 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.
@ -220,7 +190,6 @@ All contributors must sign the CNCF CLA, as described [here](CLA.md).
[sig charter process]: /committee-steering/governance/README.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
[annual community group health check]: /committee-steering/governance/annual-reports.md
[KEP process]: https://github.com/kubernetes/enhancements/tree/master/keps#kubernetes-enhancement-proposals-keps

3
liaisons.md
View File

@ -25,7 +25,7 @@ the Steering Committee.
Liaisons are assigned community groups at random (adjustments can be
made, if needed) with each member having an (almost) equal distribution
of SIGs, WGs and UGs. Each year after Steering Committee elections, new
of SIGs and WGs. Each year after Steering Committee elections, new
members will assume one of the departing members groups.
| Community Group | Steering Committee Liaison |
@ -60,7 +60,6 @@ members will assume one of the departing members groups.
| [WG LTS](wg-lts/README.md) | TBD (**[@TBD](https://github.com/TBD)**) |
| [WG Policy](wg-policy/README.md) | Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) |
| [WG Structured Logging](wg-structured-logging/README.md) | Nabarun Pal (**[@palnabarun](https://github.com/palnabarun)**) |
| [UG VMware Users](ug-vmware-users/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
| [Committee Code of Conduct](committee-code-of-conduct/README.md) | Tim Pepper (**[@tpepper](https://github.com/tpepper)**) |
| [Committee Security Response](committee-security-response/README.md) | Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**) |
<!-- BEGIN CUSTOM CONTENT -->

1
mentoring/programs/contributor-workshop/live-workshop/community-groups.md
View File

@ -17,7 +17,6 @@ Refer to previous workshops for inspirations.
- SIGs
- Subprojects
- Working Groups
- User Groups
- Committees
- How to Join Any Of The Above

8
sig-list.md
View File

@ -2,7 +2,7 @@
title: Community Groups
linkTitle: Community Groups
description: |
A list of our community groups: Special Interest Groups, Working Groups, User Groups and Committees.
A list of our community groups: Special Interest Groups, Working Groups and Committees.
weight: 99
type: docs
aliases: [ "/groups", "/sigs" ]
@ -68,12 +68,6 @@ When the need arises, a [new SIG can be created](sig-wg-lifecycle.md)
|[Policy](wg-policy/README.md)|[policy](https://github.com/kubernetes/kubernetes/labels/wg%2Fpolicy)|* Architecture<br>* Auth<br>* Multicluster<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Jim Bugwadia](https://github.com/JimBugwadia), Kyverno/Nirmata<br>* [Robert Ficcaglia](https://github.com/rficcaglia), SunStone<br>|* [Slack](https://kubernetes.slack.com/messages/wg-policy)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-policy)|* Regular WG Meeting: [Wednesdays at 8:00 PT (Pacific Time) (semimonthly)](https://zoom.us/j/7375677271)<br>
|[Structured Logging](wg-structured-logging/README.md)|[structured-logging](https://github.com/kubernetes/kubernetes/labels/wg%2Fstructured-logging)|* API Machinery<br>* Architecture<br>* Cloud Provider<br>* Instrumentation<br>* Network<br>* Node<br>* Scheduling<br>* Storage<br>|* [Patrick Ohly](https://github.com/pohly), Intel<br>* [Marek Siarkowicz](https://github.com/serathius), Google<br>|* [Slack](https://kubernetes.slack.com/messages/wg-structured-logging)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-wg-structured-logging)|* Regular Meeting: [Thursdays at 15:30 London-UK (biweekly)](https://zoom.us/j/96716142646?pwd=VmgrN29sbmhDREp3R0NtZlpGSlZ4Zz09)<br>
### User Groups
| Name | Label |Organizers | Contact | Meetings |
|------|-------|------------|--------|----------|
|[VMware Users](ug-vmware-users/README.md)|[vmware-users](https://github.com/kubernetes/kubernetes/labels/ug%2Fvmware-users)|* [Steve Wong](https://github.com/cantbewong), VMware<br>* [Myles Gray](https://github.com/mylesagray), VMware<br>|* [Slack](https://kubernetes.slack.com/messages/ug-vmware)<br>* [Mailing List](https://groups.google.com/forum/#!forum/kubernetes-ug-vmware)|* Regular User Group Meeting: [Thursdays at 11:00 PT (Pacific Time) (monthly)](https://docs.google.com/document/d/1ujpqj4hhcIBrSCK2qn6J1r--3QyD96rfDjXTZQ7n7Mw/edit)<br>
### Committees
| Name | Label | Members | Contact |

26
sig-wg-lifecycle.md
View File

@ -1,6 +1,6 @@
## SUMMARY:
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].
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].
Out of scope for this document: [subproject] creation.
[Creation]
@ -25,19 +25,6 @@ Out of scope for this document: [subproject] creation.
- [ ] 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
### Prerequisites for a UG
- [ ] Read the [documentation on user group governance](committee-steering/governance/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 dev@kubernetes.io 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`
@ -58,7 +45,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. [mailing-list-guidelines.md]
- Create one mailing list for your members and another for your chairs/leads
- Example: kubernetes-[sig/wg/ug]-foo@googlegroups.com and kubernetes-[sig/wg/ug]-foo-leads@googlegroups.com
- Example: kubernetes-[sig/wg]-foo@googlegroups.com and kubernetes-[sig/wg]-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]
@ -84,19 +71,14 @@ 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 dev@kubernetes.io 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/UG calendar
- [ ] Ensure that the [youtube-guidelines.md] links are removed and you've uploaded all SIG/WG/UG meetings to date
- [ ] 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
- [ ] 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

37
sigs.yaml
View File

@ -3330,42 +3330,7 @@ workinggroups:
liaison:
github: palnabarun
name: Nabarun Pal
usergroups:
- dir: ug-vmware-users
name: VMware Users
mission_statement: >
The VMware User Group facilitates communication among Kubernetes users and contributors
on topics pertaining to running all conformant forms of Kubernetes on VMware infrastructure.
label: vmware-users
leadership:
chairs:
- github: cantbewong
name: Steve Wong
company: VMware
- github: mylesagray
name: Myles Gray
company: VMware
tech_leads:
- github: brysonshepherd
name: Bryson Shepherd
company: Walmart
- github: phenixblue
name: Joe Searcy
company: T-Mobile
meetings:
- description: Regular User Group Meeting
day: Thursday
time: "11:00"
tz: PT (Pacific Time)
frequency: monthly
url: https://docs.google.com/document/d/1ujpqj4hhcIBrSCK2qn6J1r--3QyD96rfDjXTZQ7n7Mw/edit
contact:
slack: ug-vmware
mailing_list: https://groups.google.com/forum/#!forum/kubernetes-ug-vmware
liaison:
github: tpepper
name: Tim Pepper
usergroups: []
committees:
- dir: committee-code-of-conduct
name: Code of Conduct