diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-11-27 14:46:01 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-11-27 14:46:01 -0800 |
| commit | f47c623361ddf70d78ebf20eabb8d69df152bbac (patch) | |
| tree | f6dc6590d7b0be425dc7b7d3692653f2314678a4 | |
| parent | 41dd592c4016788adb24ca90faa35ca0bf186ec6 (diff) | |
| parent | 1370cb01f43f06cf600514bde11e7c6f2871558e (diff) | |
Merge pull request #1424 from derekwaynecarr/sponsorship
Automatic merge from submit-queue.
members must have sponsors that span organizations
This was a discussion topic with @calebamiles @smarterclayton and myself.
The previous guidance was that sponsors across organizations results in gold star, but this guidance firms up that requirement. I am in favor of this change as a way of demonstrating integration into the broader community.
Opening for others input.
| -rw-r--r-- | community-membership.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/community-membership.md b/community-membership.md index 4579e9c5..24795243 100644 --- a/community-membership.md +++ b/community-membership.md @@ -64,7 +64,7 @@ Members are expected to 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) - - Not a requirement, but having sponsorship from a reviewer from another company is encouraged (you get a gold star). + - Sponsors must be from multiple member companies to demonstrate integration across community. - Send an email to *kubernetes-membership@googlegroups.com* with: - CC: your sponsors on the message - Subject: `REQUEST: New membership for <your-GH-handle>` |