Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document process for proposing changes to SIG/WG/UG leadership #5291

Merged
merged 1 commit into from
Nov 11, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 48 additions & 0 deletions contributors/chairs-and-techleads/leadership-changes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# Leadership Changes

This document covers steps needed to propose changes to SIG/WG/UG leadership.

- [ ] Discuss the proposed changes with the current leadership.

- [ ] Send an email to the SIG/WG/UG mailing list and cc the [kubernetes-dev]
mailing list. At a minimum, the email should contain:
- [ ] intent to step down as the current lead
- [ ] if nominating another lead
- [ ] 1-2 lines about why they are being nominated
- [ ] contacts to privately reach out to for questions (current leads)
or concerns (current leads + [steering-private]) about the nomination
- [ ] if this was discussed in a meeting, link to meeting notes
- [ ] lazy consensus deadline of at least one week

- [ ] If nominating another lead, ensure that they
- [ ] are a Kubernetes GitHub org [member]
- [ ] have completed the [Inclusive Leadership Training]

nikhita marked this conversation as resolved.
Show resolved Hide resolved
- [ ] Once lazy consensus has been achieved, update the following
files in the respective repos:
nikhita marked this conversation as resolved.
Show resolved Hide resolved
- [ ] [kubernetes/community]: [`sigs.yaml`] and use the [generator doc]
to update `README.md` and `OWNERS_ALIASES` files
- [ ] [kubernetes/org]: `OWNERS_ALIASES`, [milestone-maintainers team],
kubernetes and kubernetes-sigs [team configs]
- [ ] [kubernetes/enhancements]: `OWNERS_ALIASES`

- [ ] Update all communication properties used by the community group.
See [sig-wg-lifecycle.md] for details.

Note: If multiple candidates are running for an open lead position and
lazy consensus cannot be achieved, an election should be held.
SIG Contributor Experience should be contacted to assist with the
administration of the election.

[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev
[steering-private]: steering-private@kubernetes.io
[member]: /community-membership.md#member
[`sigs.yaml`]: /sigs.yaml
[generator doc]: /generator
[kubernetes/community]: https://github.com/kubernetes/community
[kubernetes/org]: https://github.com/kubernetes/org
[kubernetes/enhancements]: https://github.com/kubernetes/enhancements
[milestone-maintainers team]: https://git.k8s.io/org/config/kubernetes/sig-release/teams.yaml
[team configs]: https://git.k8s.io/org/config
[Inclusive Leadership Training]: https://training.linuxfoundation.org/training/inclusive-speaker-orientation/
[sig-wg-lifecycle.md]: /sig-wg-lifecycle.md