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 List: rotate SIG Release tech leads and chairs #5286

Merged
merged 1 commit into from
Nov 13, 2020

Conversation

tpepper
Copy link
Member

@tpepper tpepper commented Nov 2, 2020

Periodic rotation of new folks up and into leadership roles and existing
chair out to emeritus.

Signed-off-by: Tim Pepper tpepper@vmware.com

@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Nov 2, 2020
@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Nov 2, 2020
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Yay! 🥳

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 2, 2020
@tpepper
Copy link
Member Author

tpepper commented Nov 3, 2020

Could be approved by any steering or https://github.com/kubernetes/community/blob/master/OWNERS but since it's SIG Release context and they're some of the key folks who inspired me and I followed into this space:

/assign @jdumars @calebamiles

@nikhita
Copy link
Member

nikhita commented Nov 3, 2020

@tpepper this is a little last minute, but could you also send an email to k-dev+ other steps as mentioned in #5291? It still needs to be merged but we want to follow that process for leadership changes going forward.

@nikhita
Copy link
Member

nikhita commented Nov 3, 2020

/hold
for #5286 (comment)

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 3, 2020
@tpepper
Copy link
Member Author

tpepper commented Nov 3, 2020

Will do!

@tpepper
Copy link
Member Author

tpepper commented Nov 3, 2020

For the record in this PR I want to note that Sascha is:

  • a GitHub org member
  • has completed the inclusivity training

@saschagrunert
Copy link
Member

  • has completed the inclusivity training

Yep, this is the certificate for reference: cert.pdf

@justaugustus
Copy link
Member

justaugustus commented Nov 3, 2020

@tpepper -- Thank you immensely for all of the work you've done for SIG Release and the calm and thoughtful leadership you've shown throughout. It was an absolute honor to serve together with you as a Chair and we welcome you into the revered Emeritus halls of SIG Release. 💕

@saschagrunert @hasheddan -- It's been such a pleasure to see you both learn and grow as leaders in SIG Release and I'm looking forward to going even further with you in 2021!

For SIG Release:
/lgtm
/approve

cc: @kubernetes/sig-release

@tpepper
Copy link
Member Author

tpepper commented Nov 3, 2020

Since there's a lot going on at the moment, I'm proposing a lazy consensus on this PR of EOD Friday November 13, slightly more than the one week minimum required in #5291.

Copy link
Contributor

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Thanks for all of the work you have done @tpepper!

I have completed the training and my certificate number is LF-atf7f043jq.

@justaugustus
Copy link
Member

I've opened two tracking issues (since there are some additional things that SIG Release looks after that we need to account for):

Periodic rotation of new folks up and into leadership roles and existing
chair out to emeritus.

Signed-off-by: Tim Pepper <tpepper@vmware.com>
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 13, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 13, 2020
@justaugustus
Copy link
Member

We've hit the lazy consensus deadline on this leadership rotation.
Thank you again, @tpepper! 💕
/lgtm
/approve
/hold cancel

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Nov 13, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, hasheddan, justaugustus, saschagrunert, tpepper

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

The pull request process is described 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 13, 2020
@k8s-ci-robot k8s-ci-robot merged commit 768a5e0 into kubernetes:master Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. 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

9 participants