forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update community membership procedure
- Loading branch information
Showing
1 changed file
with
17 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -41,58 +41,24 @@ Members are expected to remain active contributors to the community. | |
| - Contributing to SIG, subproject, or community discussions (e.g. meetings, Slack, email discussion | ||
| forums, Stack Overflow) | ||
| - Subscribed to [[email protected]] | ||
| - Have read the [contributor guide] | ||
| - Actively contributing to 1 or more subprojects. | ||
| - 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 from multiple member companies to demonstrate integration across community. | ||
| - Send an email to *[email protected]* with: | ||
| - CC: your sponsors on the message | ||
| - Subject: `REQUEST: New membership for <your-GH-handle>` | ||
| - Body: Confirm that you have joined [email protected] (e.g. `I have joined | ||
| [email protected]`) | ||
| - Body: Your GitHub handle | ||
| - Body: GitHub handles of sponsors | ||
| - Body: List of contributions (PRs authored / reviewed, Issues responded to, etc) | ||
| - **[Open an issue][membership request] against the kubernetes/org repo** | ||
| - Ensure your sponsors are @mentioned on the issue | ||
| - Complete every item on the checklist ([preview the current version of the template][membership template]) | ||
| - Make sure that the list of contributions included is representative of your work on the project. | ||
| - Have your sponsoring reviewers reply confirmation of sponsorship: `+1` | ||
| - Wait for response to the message | ||
| - Have read the [developer guide] | ||
|
|
||
| Example message: | ||
|
|
||
| ``` | ||
| To: [email protected] | ||
| CC: <sponsor1>, <sponsor2> | ||
| Subject: REQUEST: New membership for <your-GH-handle> | ||
| Body: | ||
| I have joined [email protected]. | ||
| My GitHub handle: | ||
| - <GH handle> | ||
| Sponsors: | ||
| - <GH handle> / <email> | ||
| - <GH handle> / <email> | ||
| List of contributions: | ||
| - <PR reviewed / authored> | ||
| - <PR reviewed / authored> | ||
| - <PR reviewed / authored> | ||
| - <Issue responded to> | ||
| - <Issue responded to> | ||
| ``` | ||
| - Once your sponsors have responded, your request will be reviewed. Any missing information will be requested. | ||
|
|
||
| ### Kubernetes Ecosystem | ||
|
|
||
| There are related Kubernetes GitHub organizations, such as [kubernetes-sigs]. We are currently working on | ||
| automation that would transfer membership in the Kubernetes organization to any related orgs automatically, | ||
| but such is not the case currently. If you are a Kubernetes org member, you are implicitly eligible for | ||
| membership in related orgs, and can request membership when it becomes relevant, by sending an email to | ||
| *[email protected]*, as outlined above. | ||
| There are related [Kubernetes GitHub organizations], such as [kubernetes-sigs]. We are currently working on automation that would transfer membership in the Kubernetes organization to any related orgs automatically, but such is not the case currently. If you are a Kubernetes org member, you are implicitly eligible for membership in related orgs, and can request membership when it becomes relevant, by [opening an issue][membership request] against the kubernetes/org repo, as above. | ||
|
|
||
| ### Responsibilities and privileges | ||
|
|
||
|
|
@@ -236,12 +202,15 @@ The following apply to the subproject for which one would be an owner. | |
|
|
||
| The Maintainer role has been removed and replaced with a greater focus on [OWNERS]. | ||
|
|
||
| [code reviews]: contributors/devel/collab.md | ||
| [community expectations]: contributors/guide/community-expectations.md | ||
| [developer guide]: contributors/devel/README.md | ||
| [two-factor authentication]: https://help.github.com/articles/about-two-factor-authentication | ||
| [code reviews]: /contributors/devel/collab.md | ||
| [community expectations]: /contributors/guide/community-expectations.md | ||
| [contributor guide]: /contributors/guide/README.md | ||
| [Kubernetes GitHub organizations]: /github-management#actively-used-github-organizations | ||
| [[email protected]]: https://groups.google.com/forum/#!forum/kubernetes-dev | ||
| [sigs.yaml]: sigs.yaml | ||
| [New contributors]: https://github.com/kubernetes/community/blob/master/CONTRIBUTING.md | ||
| [OWNERS]: contributors/guide/owners.md | ||
| [kubernetes-sigs]: https://github.com/kubernetes-sigs | ||
| [membership request]: https://github.com/kubernetes/org/issues/new?template=membership.md&title=REQUEST%3A%20New%20membership%20for%20%3Cyour-GH-handle%3E | ||
| [membership template]: https://git.k8s.io/org/.github/ISSUE_TEMPLATE/membership.md | ||
| [New contributors]: /CONTRIBUTING.md | ||
| [OWNERS]: /contributors/guide/owners.md | ||
| [sigs.yaml]: /sigs.yaml | ||
| [two-factor authentication]: https://help.github.com/articles/about-two-factor-authentication | ||