-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Stepping down from sig service catalog, add Konstantin as a co-chair #5228
Conversation
@mszostok Thanks for all your efforts with running sig service catalog! :) @jhvs Congratulations!! 🎉 We've been discussing how to improve communicating changes in SIG leadership in the steering committee - kubernetes/steering#179. We haven't documented any process changes yet but could you also send an email to the SIG Service Catalog mailing list and cc k-dev with a heads up and maybe a 2 day lazy consensus period? An example - https://groups.google.com/g/kubernetes-sig-contribex/c/fHJe36rjOdI/m/20v_vrqBBwAJ :) /hold |
Hi @nikhita! Thanks for the information, I will send email today about those changes :) |
c5996f5
to
58b02e7
Compare
/lgtm |
/lgtm |
@nikhita looks like notifications were sent a few days ago. Can we merge this now? |
Yes. For the record, here are the notifications to the mailing lists:
Welcome, @jhvhs and thanks for everything, @mszostok! /hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mszostok, nikhita 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 |
I'm leaving the project and Konstantin was selected as the new co-chair 🎉
It was awesome to be part of the SIG Service Catalog, wish you all the best! Special thanks to @jberkhahn!
Here's to new adventures! 🚀
@jberkhahn
@jhvhs