REQUEST: New membership for misterikkit

[misterikkit]

GitHub Username

@misterikkit

Organization you are requesting membership in

@kubernetes-csi

Requirements

• I have reviewed the community membership guidelines (https://git.k8s.io/community/community-membership.md)
• I have enabled 2FA on my GitHub account (https://github.com/settings/security)
• I have subscribed to the kubernetes-dev e-mail list (https://groups.google.com/forum/#!forum/kubernetes-dev)
• I am actively contributing to 1 or more Kubernetes subprojects
• I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

• @msau
• @pohly

List of contributions to the Kubernetes project

• PRs reviewed / authored
  • E2E: Add missing Bootstrap() call kubernetes#83255
  • sanity: fix nil pointer error for IDGen when using Ginkgo suite kubernetes-csi/csi-test#220
  • storage E2E: test drivers must have DNS-1123 names kubernetes#82955
  • Use reservoir sampling to select one host from priority list kubernetes#78009
  • Refactor CSI Translation Library into a struct that is injected into various components to simplify unit testing  kubernetes#82683
  • Add volume level serialization for controller operations kubernetes-sigs/gcp-compute-persistent-disk-csi-driver#316
  • Trace step should be at the end of calls rather than the begin. kubernetes#78280
  • More consistent env var handling in vsphere e2e test kubernetes#79945
  • feat: use scheduler.New in daemonset integration test kubernetes#79417
  • ...
• Issues responded to
  • Scheduler Cleanup kubernetes#68951
  • no scheduler logs whether the pod scheduler successed or failed kubernetes#67589
  • Kubernetes scheduler fails to schedule pods on nodes with enough resources. kubernetes#37232
  • Scheduler: affinity predicates read nodes from informer cache instead of scheduler cache kubernetes#75617
  • ...
• SIG projects I am involved with
  • storage
  • scheduling (former member)

[mrbobbytables]

@misterikkit Just an FYI - as a member of the kubernetes org, you don't need to seek sponsors for sub orgs like kubernetes-sigs or kubernetes-csi :)

With that said, I've added you to the org and once #1254 merges you should get a membership invite notification 👍

/assign

[misterikkit]

Thanks, Bob. What would have been the correct process, to write that PR myself? If so, we probably need a readme somewhere.

…

On Wed, Oct 2, 2019, 9:44 PM Kubernetes Prow Robot ***@***.***> wrote: Closed #1249 <#1249> via #1254 <#1254>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1249?email_source=notifications&email_token=AANWVKRWOK52WAFGSTBXL2LQMV2B3A5CNFSM4I437HLKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOT7T4KJY#event-2682766631>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANWVKWF2OJTXS422KR32M3QMV2B3ANCNFSM4I437HLA> .

[mrbobbytables]

It's touched on in the kubernetes ecosystem part of the community membership guidelines. It doesn't explicitly state that you can PR it yourself, but states as a member of kubernetes you have implicit permission to join any other org. It could likely benefit from some further clarification.