-
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 chrigl #251
Comments
I can only +1 for @kubernetes-sigs |
+1 from me! |
1 similar comment
+1 from me! |
@chrigl. Unfortunately, @flaper87 cannot sponsor you for membership in the @kubernetes org, but CAN sponsor you for the @kubernetes-sigs org. An approver/reviewer in @kubernetes, may sponsor someone for the @kubernetes org or any of the related organizations (@kubernetes-sigs, @kubernetes-incubator etc); as long as its 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-sigs cannot sponsor someone for membership in @kubernetes. They are scoped just to the org they're associated with. If you'd like to amend your request to just @kubernetes-sigs, we can proceed with getting your membership processed. Otherwise, if you could, please find another sponsor from the @kubernetes org. If you have any questions don't be afraid to ask. Thanks! |
@mrbobbytables Does https://github.com/kubernetes/cloud-provider-openstack/blob/master/OWNERS not count for @flaper87 being considered as an approver/reviewer within @kubernetes, or do you have to be an approver/reviewer within k/k? |
@chaosaffe It does! My mistake, I must have copied @flaper87 's handle wrong when doing the search to verify. >_< Sorry about that. I'll get a PR out the door soon. |
All good, thanks for the super-quick follow up ;)
…On Mon, Nov 19, 2018 at 8:22 PM Bob Killen ***@***.***> wrote:
@chaosaffe <https://github.com/chaosaffe> It does! My mistake, I must
have copied @flaper87 <https://github.com/flaper87> 's handle wrong when
doing the search to verify. >_< Sorry about that.
I'll get a PR out the door soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#251 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APFttI1s_93a_bskJ1cTbC5yMJCXfWxyks5uwwTkgaJpZM4YpSsI>
.
|
@chrigl My apologies about the confusion regarding @flaper87's sponsorship. I've created PR #253 to add you to both the @kubernetes and @kubernetes-sigs orgs. Once that gets merged, you should get a membership invite notification for both orgs :) Welcome to @kubernetes 🎉 /assign |
Thanks everyone :) |
GitHub Username
@chrigl
Organization you are requesting membership in
@kubernetes
@kubernetes-sigs
Requirements
Sponsors
List of contributions to the Kubernetes project
PRs reviewed / authored
Cluster actuator kubernetes-sigs/cluster-api-provider-openstack#94
Rename the machine actuator constructor kubernetes-sigs/cluster-api-provider-openstack#100
Generate bootstrap token kubernetes-sigs/cluster-api-provider-openstack#89
Added Role to kube-system to allow CAP-OS to create secrets kubernetes-sigs/cluster-api-provider-openstack#95
Issues responded to
Implement basic cluster actuator kubernetes-sigs/cluster-api-provider-openstack#106
Orphaned pods fail to get cleaned up kubernetes#38498
SIG projects I am involved with
/area github-membership
The text was updated successfully, but these errors were encountered: