-
Notifications
You must be signed in to change notification settings - Fork 693
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
REQUEST: New membership for ipochi #4368
Comments
/lgtm |
Looking at the bulleted list, I see |
/cc @rata |
I can happily sponsor @ipochi , I work at Microsoft :) |
Whats the next step, who approves this PR ? |
+1 from me as well. @ipochi has been doing excellent work on the apiserver network proxy project, happy to sponsor if needed (i am from red hat), |
/assign @ipochi, thank you for all your contributions so far 🙂 I've created PR #4381 to add you to the Kubernetes(s) Org. Once that gets merged, you should get a membership invite notification. Welcome to @kubernetes! 🎉 |
It seems I'm only made part of the kubernetes-sigs org and not the kubernetes org |
Hi @ipochi, you're already a member of the Kubernetes org 🙂 https://github.com/kubernetes/org/blob/main/config/kubernetes/org.yaml#L632 |
Ah so that's why I was wondering why I am going through this membership process again. This time its only for kubernetes-sigs. Thanks for that 😌 |
GitHub Username
ipochi
Organization you are requesting membership in
kubernetes, kubernetes-sigs
Requirements
Sponsor 1
cheftako
Sponsor 2
rata
List of contributions to the Kubernetes project
SIG projects I'm involved with: kubernetes-sigs/apiserver-network-proxy
Issues:
kubernetes-sigs/apiserver-network-proxy/issues/495,kubernetes-sigs/apiserver-network-proxy/issues/474,kubernetes-sigs/apiserver-network-proxy/issues/478,kubernetes-sigs/apiserver-network-proxy/issues/458,kubernetes-sigs/apiserver-network-proxy/issues/455,kubernetes-sigs/apiserver-network-proxy/issues/412,kubernetes-sigs/apiserver-network-proxy/issues/372,kubernetes-sigs/apiserver-network-proxy/issues/311
PRs:
kubernetes-sigs/apiserver-network-proxy/pull/507,kubernetes-sigs/apiserver-network-proxy/pull/485,kubernetes-sigs/apiserver-network-proxy/pull/506,kubernetes-sigs/apiserver-network-proxy/pull/479,kubernetes-sigs/apiserver-network-proxy/pull/475,kubernetes-sigs/apiserver-network-proxy/pull/381,
The text was updated successfully, but these errors were encountered: