summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2020-07-06 12:47:57 -0700
committerGitHub <noreply@github.com>2020-07-06 12:47:57 -0700
commiteba5c0f4a315116247d64bc1cea89107aa4907c2 (patch)
tree4811782889e69519fbe9f20e895568ba6ab6b3a7
parentb8d69cf427bc65c09af2de2cccf68fe259c49863 (diff)
parentccde448d15ce3a45cbe131b27466fe6c5f434b42 (diff)
Merge pull request #4915 from nikhita/membership-criteria-update
Update docs to suggest creating PRs in k/org for kubernetes members
-rw-r--r--community-membership.md6
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.