From c584d7aa187d05efa1e173781dc4c90f103d055c Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Thu, 14 Feb 2019 20:56:30 +0530 Subject: github-management: clarify sponsorship criteria An approver/reviewer in @kubernetes, may sponsor someone for the kubernetes org or any of the related organizations (kubernetes-sigs, kubernetes-csi etc); as long as it's 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 the kubernetes org. They are scoped just to the org they're associated with. --- github-management/new-membership-procedure.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'github-management') diff --git a/github-management/new-membership-procedure.md b/github-management/new-membership-procedure.md index f292bfc7..ba33b76b 100644 --- a/github-management/new-membership-procedure.md +++ b/github-management/new-membership-procedure.md @@ -51,8 +51,8 @@ required to be eligible to sponsor a new member. These requirements are: then the sponsor should be a member of either that org, or main Kubernetes org (as members of the main org have implicit membership in other orgs). -- Sponsors must be a reviewer or approver in at least one OWNERS file in any - Kubernetes GitHub org. +- Sponsors must be a reviewer or approver in at least one OWNERS file in + either the [Kubernetes GitHub org] or the org they are sponsoring for. - Sponsors must be from multiple member companies to demonstrate integration across community @@ -101,3 +101,4 @@ merge. [community membership]: /community-membership.md [k-dev]: https://groups.google.com/forum/#!forum/kubernetes-dev [kubernetes/org]: https://git.k8s.io/org/ +[Kubernetes GitHub org]: https://github.com/kubernetes -- cgit v1.2.3