REQUEST: New membership for mtardy

[mtardy]

GitHub Username

@mtardy

Organization you are requesting membership in

kubernetes

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)
• OPTIONAL: I have taken the Inclusive Open Source Community Orientation course

Note: I actually have the LF "badge", I took the course in Nov 20, 2020 to see what it was about!

Sponsor 1

@PushkarJ

Sponsor 2

@IanColdwater

List of contributions to the Kubernetes project

My contributions to the project are related to sig-security, and the docs and tooling subgroup where I regularly attend the meetings and try to participate 🤗 .

Two of my non-code contributions on k/website PR were merged:

• Add warning for creating namespaces with the same name as public TLDs #31518
• Add documentation on pod-security.kubernetes.io annotations #31602

I opened one issue after the second PR:

• Reorganize the "Well-Known Labels, Annotations and Taints" reference page #31648

I am currently making modest contributions to this issue along many other persons:

• Create a security checklist for deploying a cluster #28

[PushkarJ]

@mtardy has been a regular member of SIG Security and a repeat contributor on kubernetes security related issues and PRs. He has also presented a learning session to the community on an opensource pentest tool - kdigger that he co-created!

I wholeheartedly support his membership to the Kubernetes org.

[PushkarJ]

/honk

[k8s-ci-robot]

@PushkarJ:

In response to this:

/honk

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[IanColdwater]

Mahé has been a wonderful new addition to Kubernetes SIG Security and its subprojects, and I'm honored to help sponsor to bring his enthusiasm and dedication as a member of the Kubernetes org! Wholeheartedly +1.

…

On Apr 26, 2022, at 2:42 PM, Mahé ***@***.***> wrote:  GitHub Username @mtardy Organization you are requesting membership in kubernetes 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) OPTIONAL: I have taken the Inclusive Open Source Community Orientation course Sponsor 1 @PushkarJ Sponsor 2 @IanColdwater List of contributions to the Kubernetes project My contributions to the project are related to sig-security, and the docs and tooling subgroup where I regularly attend the meetings and try to participate 🤗 . Two of my non-code contributions on k/website PR were merged: Add warning for creating namespaces with the same name as public TLDs #31518 Add documentation on pod-security.kubernetes.io annotations #31602 I opened one issue after the second PR: Reorganize the "Well-Known Labels, Annotations and Taints" reference page #31648 I am currently making modest contributions to this issue along many other persons: Create a security checklist for deploying a cluster #28 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[palnabarun]

@mtardy -- thank you for all your contributions so far :)

I've created PR #3405 to add you to the orgs. Once that gets merged, you should get a membership invite notification.

Welcome! 🎉

/assign