-
Notifications
You must be signed in to change notification settings - Fork 715
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 aojea #952
Comments
+1 |
+1. already a member of k/kuberentes-sigs so eligible for k/kubernetes too. :) |
+100000!
…On Tue, Jun 25, 2019 at 3:54 AM Lubomir I. Ivanov ***@***.***> wrote:
+1. already a member of k/kuberentes-sigs so eligible for k/kubernetes
too. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#952?email_source=notifications&email_token=AAHADKY3ZNHGW6FKAFIW3ATP4H2NRA5CNFSM4H3GOWL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYP27XA#issuecomment-505393116>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHADKZXDYAHIMFCGP53X7LP4H2NRANCNFSM4H3GOWLQ>
.
|
(As a point of clarification, membership to |
I know this is not the place to discuss this but ... I think we really should not distinguish between kubernetes-sigs and kubernetes as we move things out of the main org to kubernetes-sigs pretty aggressively. It sends a bad / the wrong message that kubernetes-sigs has a different bar as we move projects from kubernetes to kubernetes-sigs... In any case, @aojea has done a lot of wonderful and woefully understaffed work in both orgs in his spare time, thank you again! |
Thanks folks |
@BenTheElder -- I completely agree on all points and have opened #966 to discuss. As an aside, I was surprised @aojea wasn't already in the org! :) |
thanks @justaugustus!! :-) |
GitHub Username
@aojea
Organization you are requesting membership in
@kubernetes
Requirements
Sponsors
List of contributions to the Kubernetes project
PRs authored in kubernetes/kubernetes
PRs authored in kubernetes-sigs/kind
Issues responded in kubernetes/kubernetes
Issues responded in kubernetes-sigs/kind
https://github.com/kubernetes-sigs/kind
The text was updated successfully, but these errors were encountered: