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

sig-cloud-provider: move andrewsykim and nckturner to emeritus status add elmiko as TL #7815

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrewsykim
Copy link
Member

move andrewsykim and nckturner to emeritus status add elmiko as TL

…, add elmiko as TL

Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

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

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 10, 2024
@k8s-ci-robot k8s-ci-robot added sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 10, 2024
@elmiko
Copy link
Contributor

elmiko commented Apr 10, 2024

i am happy to serve as an interim technical lead to help facilitate the change, but i would feel more comfortable about adding another member from the community as well.

also, do we need to announce this change on the mailing list before we merge the PR?

@elmiko
Copy link
Contributor

elmiko commented Apr 10, 2024

cc @bridgetkromhout @cheftako

@cblecker
Copy link
Member

/hold
/committee steering

The process for leadership changes is here (and does include some email steps): https://github.com/kubernetes/community/blob/master/contributors/chairs-and-techleads/leadership-changes.md

There's also a handy issue template with a checklist: https://github.com/kubernetes/community/issues/new/choose

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. committee/steering Denotes an issue or PR intended to be handled by the steering committee. labels Apr 10, 2024
@elmiko
Copy link
Contributor

elmiko commented Apr 10, 2024

thanks @cblecker , i seem to remember us missing some steps on this the last time, so i wanted to make sure we observe the proper process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. committee/steering Denotes an issue or PR intended to be handled by the steering committee. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants