REQUEST: New membership for @hardikdr

[hardikdr]

GitHub Username

@hardikdr

Organization you are requesting membership in

@kubernetes-sigs
@kubernetes

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

• @roberthbailey
• @chaosaffe
• @nikhita

List of contributions to the Kubernetes project

• PRs reviewed / authored

  • Bugfix: Update AddNodeHandler error logs kubernetes#54385
  • Update version for PriorityClass website#9321
  • Add node-conditions to the MachineStatus kubernetes-sigs/cluster-api#483
  • Add apis for machine-class kubernetes-sigs/cluster-api#488
  • Update README to include API adoption kubernetes-sigs/cluster-api#511
  • Add APIs for machine phases kubernetes-sigs/cluster-api#531

• Issues responded to

  • Scheduler should consider the current status of cpu/memory of hosts while scheduling. kubernetes#12455
  • Separate Machine APIs from Cluster APIs kubernetes-sigs/cluster-api#490
  • Define health check strategy for MachineSet kubernetes-sigs/cluster-api#47
  • Update version for PriorityClass website#9321

• SIG projects I am involved with https://github.com/kubernetes-sigs/cluster-api

/area github-membership

[scruplelesswizard]

+1 from me!

@hardikdr Thank you for all your work so far, and happy to have you as part of the org 😍

[roberthbailey]

+1 from me

[mrbobbytables]

Hey there @hardikdr. Unfortunately, @chaosaffe 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!

[nikhita]

+1

I am happy to act as a sponsor for @hardikdr. He has made numerous contributions to the Cluster API subproject and is an active participant in meetings. He has also written a proposal for a feature.

Also, just for complete clarity, I am listed in the following OWNERS files: https://cs.k8s.io/?q=nikhita&i=fosho&files=OWNERS&repos=

[hardikdr]

Thanks a lot @nikhita, for being a sponsor 🙂

@mrbobbytables Thank you for clarification. I updated the Issue to include @nikhita as a sponsor. Please let me know if there is anything required yet. 🙂

[cblecker]

Invite will be sent out as soon as #220 merges. Welcome to @kubernetes! 🚀