-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document process for proposing changes to SIG/WG/UG leadership
- Loading branch information
Showing
1 changed file
with
48 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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] | ||
|
||
- [ ] Once lazy consensus has been achieved, updating the following | ||
files in the respective repos: | ||
- [ ] [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 |