-
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 PrasadG193 #5019
Comments
@xing-yang, a +1 after you review this request, would help me process this one. Thank you :) |
@bswartz, i looked up but I was unable to find you in an OWNERS file. (a requisite for being a sponsor). Would you point me to a place you’re listed in, in case I overlooked it? Failing which, @PrasadG193 might have to look for another sponsor. |
Which owners file are you looking in? I clicked on that link and I can't see what the requirements are for the csi group. |
I was pointing to this subpoint in the requirements.
A listing in any OWNERS file in the kubernetes orgs should be fine for me to go ahead. (co sponsor Xing Yang, is listed here, for example: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-csi/OWNERS) |
These are the things I own:
They are all tangential to the main kubernetes project. It's up to you to interpret the rules in this case. If the rules require someone that owns code in kubernetes proper we'll need another sponsor. |
@bswartz, no this is exactly it. I’m sorry I missed them. Thank you very much |
For the record, I +1 this membership |
/assign @PrasadG193, thank you for all your contributions. Looking forward to so much more 🙂 I’ve created PR #5027 to add you to the Kubernetes(s) Org. Once that gets merged, you should get a membership invite notification. Welcome to @kubernetes! 🎉 |
Thank you!! 🙏 |
Looks like I missed this. +1 |
GitHub Username
@PrasadG193
Organization you are requesting membership in
kubernetes-csi
Requirements
Sponsor 1
@xing-yang
Sponsor 2
@bswartz
List of contributions to the Kubernetes project
The text was updated successfully, but these errors were encountered: