diff options
| -rw-r--r-- | community-membership.md | 18 | ||||
| -rw-r--r-- | sig-cli/CONTRIBUTING.md | 9 |
2 files changed, 3 insertions, 24 deletions
diff --git a/community-membership.md b/community-membership.md index 1b51cd56..ebdb0c2e 100644 --- a/community-membership.md +++ b/community-membership.md @@ -19,24 +19,6 @@ scoped by these sub-areas. [**New contributors**](https://github.com/kubernetes/contrib/issues/1090) should be welcomed to the community by existing members, helped with PR workflow, and directed to relevant documentation and communication channels. -**Note:** Individuals may be added as an outside collaborator (with READ access) to a repo in the Kubernetes GitHub -organization without becoming a member. This will allow them to be assigned issues and PRs until they become a member, -but will not allow tests to be run against their PRs automatically nor allow them to interact with the PR bot. - -### Requirements for outside collaborators - -- Working on some contribution to the project that would benefit from - the ability to have PRs or Issues to be assigned to the contributor -- Have the support of 1 member - - Find a member who will sponsor you - - Send an email to kubernetes-membership@googlegroups.com - - CC: your sponsor - - Subject: `REQUEST: New outside collaborator for <your-GH-handle>` - - Body: GitHub handle of sponsor - - Body: Justification - any contributions or what you will be working on - - Have your sponsoring member reply confirmation of sponsorship: `+1` - - Wait for response to the message - ## Established community members Established community members are expected to demonstrate their adherence to the principles in this diff --git a/sig-cli/CONTRIBUTING.md b/sig-cli/CONTRIBUTING.md index d650665f..10dc3421 100644 --- a/sig-cli/CONTRIBUTING.md +++ b/sig-cli/CONTRIBUTING.md @@ -114,16 +114,13 @@ assigned to them: **Note:** Don't do this unless you will start work on the issue within a few days of being assigned. **Note:** GitHub only allows issues to be assigned to GitHub accounts that are part -of the organization or listed as outside collaborators. In order to become an outside -collaborator, contributors have to have shown commitment to the issue by performing some -work. Once you have begun, reach out to the issue author and show them your progress -(e.g. in a fork). +of the organization. **Picking your first issue** For your first issue, we recommend picking an issue labeled with "good first issue" from the [issue] backlog. -**Picking the right size of issue** +**Picking the right size of issue** Be sure to pick up an issue that is appropriate to the time you are able to commit. We recommend first time contributors start with small or medium issues. @@ -150,7 +147,7 @@ some piece of it, and if you would like to continue working on it, or have it un Guided issues have a *type* defining the type of work to be done. Pick up an issue that fits your experience level and interest. Documentation and test-coverage issues typically are smaller in scope and easier to complete than -features and cleanup issues. +features and cleanup issues. - `type/code-cleanup` - Usually some refactoring or small rewrites of code. |