diff options
| author | Nikhita Raghunath <nikitaraghunath@gmail.com> | 2020-07-05 01:10:24 +0530 |
|---|---|---|
| committer | Nikhita Raghunath <nikitaraghunath@gmail.com> | 2020-07-05 01:23:03 +0530 |
| commit | ccde448d15ce3a45cbe131b27466fe6c5f434b42 (patch) | |
| tree | b639e9741b41e13e54de8f6743bc6f88148609ec | |
| parent | 614a60473c188812abdf1465c78bc95cf32a3553 (diff) | |
Update docs to suggest creating PRs in k/org for kubernetes members
We've had many issues opened in k/org where existing `kubernetes` org
members request membership to `kubernetes-sigs`. Under our current
policy, all members of `kubernetes` are implicitly eligible for
membership to `kubernetes-sigs` and don't require sponsorship.
In such cases, we usually ask them to create a PR directly or we create
one ourselves and let the requester lgtm it. To ease the often
unneccessary two step process, this commit updates community membership
guidelines to suggest creating PRs directly if they are existing
`kubernetes` members.
| -rw-r--r-- | community-membership.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/community-membership.md b/community-membership.md index 4b5143e5..c22a4520 100644 --- a/community-membership.md +++ b/community-membership.md @@ -71,8 +71,10 @@ 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. However, if you are a member of any of the related +relevant, by creating a PR directly or [opening an issue][membership request] +against the kubernetes/org repo, as above. + +However, if you are a member of any of the related [Kubernetes GitHub organizations] but not of the [Kubernetes org], you will need explicit sponsorship for your membership request. |