-
Notifications
You must be signed in to change notification settings - Fork 703
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 kfox1111 #518
Comments
Hey there @kfox1111 , unfortunately @sbezverk cannot sponsor you for membership in the @kubernetes org, but CAN sponsor you for membership in @kubernetes-csi. An approver/reviewer in @kubernetes, may sponsor someone for the @kubernetes org or any of the related organizations (@kubernetes-sigs, @kubernetes-csi etc); as long as it's a project they're involved with. However, this does not work the other way around. A sponsor that is only an approver/reviewer in @kubernetes-csi cannot sponsor someone for membership in @kubernetes. They are scoped just to the org they're associated with. @kfox1111 If you'd like to amend your request to just @kubernetes-csi, we can proceed with getting your membership processed once @vladimirvivien and @sbezverk add their +1. Otherwise, if you could, please find another sponsor from the @kubernetes org. If you have any questions don't be afraid to ask. Thanks! |
+1
From: Bob Killen <[email protected]>
Reply-To: kubernetes/org <[email protected]>
Date: Wednesday, February 27, 2019 at 8:52 AM
To: kubernetes/org <[email protected]>
Cc: sbezverk <[email protected]>, Mention <[email protected]>
Subject: Re: [kubernetes/org] REQUEST: New membership for kfox1111 (#518)
Hey there @kfox1111<https://github.com/kfox1111> , unfortunately @sbezverk<https://github.com/sbezverk> cannot sponsor you for membership in the @kubernetes<https://github.com/kubernetes> org, but CAN sponsor you for membership in @kubernetes-csi<https://github.com/kubernetes-csi>.
An approver/reviewer in @kubernetes<https://github.com/kubernetes>, may sponsor someone for the @kubernetes<https://github.com/kubernetes> org or any of the related organizations (@kubernetes-sigs<https://github.com/kubernetes-sigs>, @kubernetes-csi<https://github.com/kubernetes-csi> etc); as long as it's a project they're involved with.
However, this does not work the other way around. A sponsor that is only an approver/reviewer in @kubernetes-csi<https://github.com/kubernetes-csi> cannot sponsor someone for membership in @kubernetes<https://github.com/kubernetes>. They are scoped just to the org they're associated with.
@kfox1111<https://github.com/kfox1111> If you'd like to amend your request to just @kubernetes-csi<https://github.com/kubernetes-csi>, we can proceed with getting your membership processed once @vladimirvivien<https://github.com/vladimirvivien> and @sbezverk<https://github.com/sbezverk> add their +1. Otherwise, if you could, please find another sponsor from the @kubernetes<https://github.com/kubernetes> org.
If you have any questions don't be afraid to ask.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#518 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APhP0Hnc5NKTPDkswcCWYJjFKbae_TIFks5vRo2YgaJpZM4bKK6f>.
|
Works for me. I'll amend it to just kubernetes-csi for now. |
+1 |
@kfox1111, thank you for all your contributions so far :) I've created PR #555 to add you to the @kubernetes-csi Org. Once that gets merged, you should get a membership invite notification. Welcome to @kubernetes-csi! 🎉 /assign |
Thank you. :) |
GitHub Username
kfox1111
Organization you are requesting membership in
kubernetes-csi
Requirements
Sponsors
List of contributions to the Kubernetes project
kubernetes/enhancements#596
kubernetes/enhancements#790
kubernetes/kubernetes#45613
kubernetes/kubernetes#33881
I can dig up more if this isn't enough.
The text was updated successfully, but these errors were encountered: