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

contributors/chairs-and-techleads/leadership-changes.md

@@ -0,0 +1,27 @@
+# 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 (usually current leads) to privately reach out
+          to for questions or concerns about the nomination
+  - [ ] if this was discussed in a meeting, link to meeting notes
+  - [ ] lazy consensus deadline of at least 2 business days
+
+- [ ] Once lazy consensus has been achieved, submit a PR to update
+[`sigs.yaml`] and use the [generator doc] to update `README.md` and
+`OWNERS_ALIASES` files.
+
+- [ ] Create an issue in the kubernetes/community repo to track
+completion of the [Inclusive Leadership Training] by the new lead(s).
+
+[kubernetes-dev]: https://groups.google.com/g/kubernetes-dev
+[`sigs.yaml`]: /sigs.yaml
+[generator doc]: /generator
+[Inclusive Leadership Training]: https://training.linuxfoundation.org/training/inclusive-speaker-orientation/