diff options
| author | Nikhita Raghunath <nikitaraghunath@gmail.com> | 2019-02-14 20:56:30 +0530 |
|---|---|---|
| committer | Nikhita Raghunath <nikitaraghunath@gmail.com> | 2019-02-14 20:58:14 +0530 |
| commit | c584d7aa187d05efa1e173781dc4c90f103d055c (patch) | |
| tree | c7ad845af96d35c86e237e38802011a9bfa6fe15 /community-membership.md | |
| parent | 665611b75a772677978e6a544690d27a20d75565 (diff) | |
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.
Diffstat (limited to 'community-membership.md')
| -rw-r--r-- | community-membership.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/community-membership.md b/community-membership.md index 7d85360d..a691e8c9 100644 --- a/community-membership.md +++ b/community-membership.md @@ -50,8 +50,8 @@ remain active contributors to the community. - Sponsored by 2 reviewers. **Note the following requirements for sponsors**: - Sponsors must have close interactions with the prospective member - e.g. code/design/proposal review, coordinating on issues, etc. - - Sponsors must be reviewers or approvers in at least 1 OWNERS file (in any repo in the Kubernetes GitHub - organization) + - Sponsors must be reviewers or approvers in at least 1 OWNERS file either in any repo in the [Kubernetes org], + or the org they are sponsoring for. - Sponsors must be from multiple member companies to demonstrate integration across community. - **[Open an issue][membership request] against the kubernetes/org repo** - Ensure your sponsors are @mentioned on the issue |