REQUEST: New membership for jnpacker

[jnpacker]

GitHub Username

jnpacker

Organization you are requesting membership in

kubernetes, 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

@RainbowMango

Sponsor 2

@yue9944882

List of contributions to the Kubernetes project

kubernetes/enhancements#5445

Reviewer.

[yue9944882]

+1 I support Joshua's membership.

[RainbowMango]

+1
100%

[jasonbraganza]

Hello @jnpacker, Membership application guidelines require existing contributions to Kubernetes upstream projects.

- Have made multiple contributions to the project or community, enough to demonstrate an ongoing and long-term commitment to the project. Contributions should include, but is not limited to:

    - Authoring or reviewing PRs on GitHub, with at least one merged PR. NOTE: The PR(s) must demonstrate an ongoing and active commitment. 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)
    - Filing or commenting on issues on GitHub
    - Contributing to SIG, subproject, or community discussions (e.g. meetings, Slack, email discussion forums)

Would you kindly include links to Kubernetes upstream contributions?
You’ll find Github orgs that can be considered for this request here.