@Adirio
@kubernetes
kubebuilder (54 at application time): linkkubebuilder (60 at application time): linkkubebuilder (50 at application time): linkkubebuilder (contributors) and related tools, belonging to sigs-api-machinery+1, @Adirio has been helping out a bunch with Kubebuilder. Time to make it official in the org 馃檪
:+1: from me as well
@Adirio did you mean the kubernetes or the kubernetes-sigs org?
@alexeldeib unfortunately cannot sponsor you for membership in the @kubernetes org, but CAN sponsor you for membership in @kubernetes-sigs.
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.
@Adirio 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 the purpose of this PR is described in https://github.com/kubernetes/test-infra/pull/17241#issuecomment-615330612
It's not actually at all related to kubernetes-sigs, it's related to test-infra, which @Adirio and I both help work on.
If that's not acceptable, is there a recommended way in the Kubernetes org to have test-infra access for kubernetes-sigs projects who have members maintaining test-infra support for those projects? Seems a bit backwards you're able to approve/review a project, contribute to its test infrastructure, but not approve/review that test infrastructure because you can't become a k/k member.
WDYT?
(n.b. I realized I'm not currently a review in k/k either, but that test-infra adds me as one -- I thought it already merged)
@mrbobbytables I'm already part of @kubernetes-sigs, I was asking for @kubernetes membership for the reason mentioned by @alexeldeib, thought he was a member.
Just to clarify, merging https://github.com/kubernetes/test-infra/pull/17241 is actually sufficient for me to approve this, right?
I pinged @Adirio offline to apologize for the confusion and let him know he's free to find another sponsor, but I'd rather just wait for the test-infra PR to merge to make this kosher.
I'm still curious about the edge case of test-infra given its nature and wide use across Kubernetes SIGs -- is this something that has been discussed?
@alexeldeib It would be -- with that in flight and sign off from @DirectXMan12 , I'm okay with moving forward on this one 馃憤
@Adirio I'll append your org membership to PR #1836 here in a minute. 馃槃
Sorry for the back and forth a bit. This has come up a few times, but in general is pretty rare.
On a lighter note...
@Adirio -- I've added you to the Kubernetes Org in #1836 . Once that gets merged, you should get a membership invite notification.
Welcome to @kubernetes! 馃帀
/assign
Most helpful comment
@alexeldeib It would be -- with that in flight and sign off from @DirectXMan12 , I'm okay with moving forward on this one 馃憤
@Adirio I'll append your org membership to PR #1836 here in a minute. 馃槃