[Ankitraj-Sharma]

Which issue(s) this PR fixes:
Fixes #9122

What this PR does:

Expands and completes contributors/chairs-and-techleads/leadership-changes.md based on the 15-item onboarding/offboarding checklist in .github/ISSUE_TEMPLATE/leadership-change.yml and the issue discussion in #9122.

Key improvements:

• Prerequisites: Clear guidelines for nominee org membership and Linux Foundation Inclusive Open Source orientation.
• Lazy Consensus: Email notification requirements (cc dev@kubernetes.io) with required fields and timeline.
• Step-by-step repository updates:
  • kubernetes/community: sigs.yaml, emeritus_leads, and using make to regenerate SIG docs/OWNERS.
  • kubernetes/org: root OWNERS_ALIASES, milestone maintainers (config/kubernetes/sig-release/teams.yaml), and SIG team configs.
  • kubernetes/enhancements: OWNERS_ALIASES for KEP reviews.
  • kubernetes/kubernetes: feature-approvers where applicable.
  • kubernetes/k8s.io: Global leads mailing list (leads@kubernetes.io) and SIG-specific leads mailing lists under groups/.
• Communications, Access, & Projects: Detailed procedures for Slack #chairs-and-techleads, shared Google Calendar, 1Password vault access via ContribEx, YouTube playlists via YouTube moderators, and GitHub project boards (.projects).

/sig contributor-experience
/kind documentation

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Ankitraj-sharma / name: Ankit raj sharma (8808228)

[kubernetes-prow]

Welcome @Ankitraj-Sharma!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Ankitraj-sharma
Once this PR has been reviewed and has the lgtm label, please assign palnabarun for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• contributors/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubernetes-prow]

Hi @Ankitraj-Sharma. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[jberkus]

Hey, thanks! I'll take a look at it as soon as I can.

Can you make sure that the PR is open to changes by repo owners? That way I can just make minor wording changes without needing you to do it.

/ok-to-test

[Ankitraj-Sharma]

Hi @jberkus,

Thank you for reviewing!

Yes, "Allow edits by maintainers" is confirmed enabled on this PR, so you and the repo maintainers have full permission to push any edits or minor wording tweaks directly to the branch.

Looking forward to your feedback!

[Ankitraj-Sharma]

*Hi @jberkus, Thank you for reviewing! Yes, 'Allow edits by maintainers' is confirmed enabled on this PR, so you and the repo maintainers have full permission to push any edits or minor wording tweaks directly to the branch. Looking forward to your feedback!*

…

On Wed, Sep 30, 2026 at 2:41 AM Josh Berkus ***@***.***> wrote: *jberkus* left a comment (kubernetes/community#9188) <#9188 (comment)> Hey, thanks! I'll take a look at it as soon as I can. Can you make sure that the PR is open to changes by repo owners? That way I can just make minor wording changes without needing you to do it. /ok-to-test — Reply to this email directly, view it on GitHub <#9188?email_source=notifications&email_token=BXFQ2TGYE26S5T5IIUULRSD5RQQO5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBZHA4TMOBTHE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5898968396>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BXFQ2TC7NAE763W7W6B2BDL5RQQO5AVCNFSNUABEKJSXA33TNF2G64TZHM2TOOJTHEYTCMR3JFZXG5LFHM2TMMZWGEYTMNBRGOQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BXFQ2TC4HQYFSTCUXYR3TNT5RQQO5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBZHA4TMOBTHE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/BXFQ2TCLILSSB4UZHTSTJY35RQQO5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKOBZHA4TMOBTHE3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>