summaryrefslogtreecommitdiff
path: root/contributors
diff options
context:
space:
mode:
authorNikhita Raghunath <nikitaraghunath@gmail.com>2020-11-03 15:02:11 +0530
committerNikhita Raghunath <nikitaraghunath@gmail.com>2020-11-05 13:50:26 +0530
commitedae8589503e945883ab3be16ca3ea2e85da66af (patch)
treee16bb328a3e93ff2a10cd2c2dd44865904e6a16e /contributors
parent08d47b6a8ceef38d7be496d952541a93fb71970d (diff)
Document process for proposing changes to SIG/WG/UG leadership
Diffstat (limited to 'contributors')
-rw-r--r--contributors/chairs-and-techleads/leadership-changes.md48
1 files changed, 48 insertions, 0 deletions
diff --git a/contributors/chairs-and-techleads/leadership-changes.md b/contributors/chairs-and-techleads/leadership-changes.md
new file mode 100644
index 00000000..2d14bd07
--- /dev/null
+++ b/contributors/chairs-and-techleads/leadership-changes.md
@@ -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, update 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