REQUEST: New membership for miouge1

[Miouge1]

GitHub Username

@Miouge1

Organization you are requesting membership in

@kubernetes-sigs

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 (on Slack this week)

Sponsors

• @dims
• @Atoms

List of contributions to the Kubernetes project

• PRs reviewed / authored
• Fix ups-broker install instructions kubernetes-retired/service-catalog#2516
• Add ClusterIP as a valid apiserver.service.type option kubernetes-retired/service-catalog#2544
• [contrib/terraform/openstack] Add support for router less deployments kubernetes-sigs/kubespray#3556
• [contrib/terraform/openstack] Add list of know working OpenStack clouds kubernetes-sigs/kubespray#3543
• Include etcd and masters in adding node doc kubernetes-sigs/kubespray#2990
• CheckNodePIDPressure is not supported in v1.10 kubernetes-sigs/kubespray#2946
• Restart scheduler when policy changes kubernetes-sigs/kubespray#2770
• Update kube-scheduler policy kubernetes-sigs/kubespray#2737
• Add Ingress variable in Grafana dashboard ingress-nginx#3050
• [grafana] Rate over 2 minutes since default Prometheus interval is 1m ingress-nginx#2884
• Issues responded to
• SIG projects I am involved with
• Kubespray

[Atoms]

+1

[dims]

+1 to from me. welcome @Miouge1

[mrbobbytables]

Hey there @Miouge1, Unfortunately @Atoms cannot sponsor you for membership in the @kubernetes org. Sponsors must be a reviewer or approver in an owners file (membership requirements).

Have you reached out to the Kubespray team? Someone from their group may be able to sponsor you for @kubernetes-sigs membership.

[Atoms]

@mrbobbytables in requirements for sponsor written:
Sponsors must be reviewers or approvers in at least 1 OWNERS file (in any repo in the Kubernetes GitHub organization)
this does not include kubespray-sigs organization? I need to be in Kubernetes Organization OWNERS file? cause i am in kubespray-sigs OWNERS file

[mrbobbytables]

@Atoms You're right! I forgot to check ignore case when searching with https://cs.k8s.io Sorry about that.

One caveat remains though, 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.

@Miouge1 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!

[Atoms]

@mrbobbytables good requirement :) I thought being just a member of Kubernetes Organization is enough :) but rereading now requirements it's clear for me :)

[Miouge1]

@mrbobbytables thank you for the explanation, I wasn't up to date with the different orgs.

@kubernetes-sigs is good enough, so I have updated the issue with that.

Thank you for your patience.

[mrbobbytables]

@Miouge1 my apologies for the back and forth, but things should be good now :)
I've created PR #416 to add you to the @kubernetes-sigs org. Once it gets merged, you should get a membership invite notification.

Welcome to @kubernetes-sigs! 🎉

/assign