-
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
SIG Network: Leadership Change #7650
Comments
add aojea to sig-net leads Ref: kubernetes/community#7650
/lgtm |
This template is missing an item for " |
Added the item manually for this issue, and then created #7661 to add it permanently to the template. |
Also @aojea just need a confirmation that you've taken https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ |
it is here https://www.credly.com/badges/5a918494-f3cd-4633-9c83-be66e8068d33/linked_in_profile |
Announced: https://groups.google.com/a/kubernetes.io/g/dev/c/Yj0NIS0yRlI/m/ZEoyizt2BgAJ Just waiting on someone who can do the calendar/group updates at some point and then all set. |
Antonio is an owner of the sig-net ML and calendar now. Unfortunately, the leads group has no Owners. I have tried to get support internally and not succeeded so far. If we want to "recover" it, we may need to make a new group and change the Zoom and other things over to it. |
Creating a managed one isn't too difficult, several SIGs have gone that way already. Just need to ping slack admins when ready to change the account email address over |
I think we can close this now @mrbobbytables @shaneutt |
Yep, we're all set I think. |
SIG/WG name:
SIG Network
Onboarding Lead(s):
aojea
Offboarding Lead(s):
No response
Link to discussion:
https://groups.google.com/g/kubernetes-sig-network/c/eXWpR97fSWc
Prerequisites for new leads:
Onboarding / Offboarding tasks:
make
). NOTE: If offboarding, remember to add to emeritus.#chairs-and-techleads
slack channel.Additional information:
No response
Labels:
/sig network
/assign @mrbobbytables
/cc @thockin @MikeZappa87 @danwinship
The text was updated successfully, but these errors were encountered: