-
Notifications
You must be signed in to change notification settings - Fork 666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REQUEST: New membership for sudermanjr #4523
Comments
@sudermanjr our community membership guidelines require showing ongoing active contributions to projects within the Kubernetes orgs; contributions to projects outside of kubernetes are not applicable.^^;; |
@mrbobbytables Are you specifically referring to the Helm contributions? Not sure what action you would like me to take from your comment |
Yes, but in addition to that there needs to be significant ongoing contributions to K8s itself to become an org member. |
Andy has been an active contributor to the Policy WG and has worked on several initiatives including building the policy report API, writing papers, and policy and governance, and updating the Kubernetes docs. The WG meeting & activity tracker is available at: I am happy to support Andy's nomination as co-chair and am looking forward to continuing to work together to help secure and scale Kubernetes. |
I'll +1 as a sponsor. I've been working with @JimBugwadia and @rficcaglia to get things sorted out for wg-policy. 👍 |
+1 on Andy as a contributor to the WG content both in the wg repo and IRL @ KubeCon at the contributor summit wg-policy session. |
GitHub Username
@sudermanjr
Organization you are requesting membership in
kubernetes, kubernetes-sigs
Requirements
Sponsor 1
@JimBugwadia
Sponsor 2
@rficcaglia
List of contributions to the Kubernetes project
I have participated in many different Kubernetes related repositories and projects throughout the years, but here's a few more recent examples:
Goldilocks work with VPA project, where we occasionally work to support issues between the two.
The text was updated successfully, but these errors were encountered: