Remove references to outside collaborators
This commit is contained in:
parent
7efcbfef3e
commit
cb4b49d55a
|
@ -19,24 +19,6 @@ scoped by these sub-areas.
|
||||||
[**New contributors**](https://github.com/kubernetes/contrib/issues/1090) should be welcomed to the community
|
[**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.
|
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
|
||||||
|
|
||||||
Established community members are expected to demonstrate their adherence to the principles in this
|
Established community members are expected to demonstrate their adherence to the principles in this
|
||||||
|
|
|
@ -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:** 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
|
**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
|
of the organization.
|
||||||
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).
|
|
||||||
|
|
||||||
**Picking your first issue**
|
**Picking your first issue**
|
||||||
|
|
||||||
For your first issue, we recommend picking an issue labeled with "good first issue" from the [issue] backlog.
|
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.
|
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.
|
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
|
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
|
issue that fits your experience level and interest. Documentation and
|
||||||
test-coverage issues typically are smaller in scope and easier to complete than
|
test-coverage issues typically are smaller in scope and easier to complete than
|
||||||
features and cleanup issues.
|
features and cleanup issues.
|
||||||
|
|
||||||
- `type/code-cleanup`
|
- `type/code-cleanup`
|
||||||
- Usually some refactoring or small rewrites of code.
|
- Usually some refactoring or small rewrites of code.
|
||||||
|
|
Loading…
Reference in New Issue