REQUEST: New membership for vmishra22

[vmishra22]

GitHub Username

@vmishra22

Organization you are requesting membership in

kubernetes-sigs

Requirements

• I have reviewed the community membership guidelines
• I have enabled 2FA on my GitHub account
• I have subscribed to the kubernetes dev e-mail list
• 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
• I have verified that my sponsors are from different member companies
• I have verified that my sponsors are a reviewer or an approver in at least one OWNERS file within one of the Kubernetes GitHub organizations (excluding the contributor-playground)
• SUGGESTED: Ensure your affiliation in gitdm is up to date (gitdm is used by devstats to track affiliation)
• SUGGESTED: Ensure your affiliation in openprofile.dev is up to date (used by LFX Insights to track affiliation, will replace gitdm in the future)
• SUGGESTED: I have taken the Inclusive Open Source Community Orientation course

Sponsor 1

@DavidXU12345

Sponsor 2

@YangjinanHu

List of contributions to the Kubernetes project

Avoid random mounttargetip for cross-account EFS mounts

Support for attachRequired in CSI driver

add e2e test for cross account setup

[YangjinanHu]

+1

[DavidXU12345]

+1

[jasonbraganza]

@vmishra22, could you point me to evidence of more work done in the project?

Community membership guidelines require a bit more work, than what is presented currently

A few examples include:

- A single [KEP](https://github.com/kubernetes/enhancements/blob/master/keps/README.md#kubernetes-enhancement-proposals-keps) that has taken several weeks of driving consensus
- A larger number of smaller PRs over several weeks to months
- A smaller number of complex or technical PRs that required working with community members to resolve an issue (e.g. regressions, bugs fixes etc)

[vmishra22]

@jasonbraganza I am working at AWS EFS team and need access for CSI driver as owner to do PR review. This will facilitate the development process immensely. Thanks.

[jasonbraganza]

@vmishra22, In which case, I would suggest working in collaboration with existing owners for a bit, as you build up to fulfilling the requirements for membership.
Please feel free to ping me when this happens and I’ll help get you sorted with the membership. Thank you :)

[jasonbraganza]

@DavidXU12345, would you kindly update your work org on your profile, or here in this issue?
Asking because membership guidelines require that sponsors be from different organisations.

Sponsored by 2 reviewers. Note the following requirements for sponsors:
  * Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc.
  * Sponsors must be reviewers or approvers in at least one OWNERS file within one of the [Kubernetes GitHub organizations](https://github.com/kubernetes/community/blob/master/github-management#actively-used-github-organizations)
  * Sponsors must be from multiple member companies to demonstrate integration across community.