diff options
| author | Carolyn Van Slyck <carolyn.vanslyck@microsoft.com> | 2018-06-09 17:19:54 -0500 |
|---|---|---|
| committer | Carolyn Van Slyck <carolyn.vanslyck@microsoft.com> | 2018-06-09 17:21:55 -0500 |
| commit | 742a0445d62e8bd359b8d5d5025d94e8a6db4559 (patch) | |
| tree | 08d3c1f6606a5eee0382c49c858fb123116087ac /contributors/guide/README.md | |
| parent | e5e4b58f36cb87435c001ba3a998e2dd8f3dd008 (diff) | |
Define good first issue and clarify help wanted labels
Diffstat (limited to 'contributors/guide/README.md')
| -rw-r--r-- | contributors/guide/README.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index ad5cf2e1..d2540117 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -72,7 +72,9 @@ You get the idea - if you ever see something you think should be fixed, you shou ### Find a good first topic There are multiple repositories within the Kubernetes community and a full list of repositories can be found [here](https://github.com/kubernetes/). -Each repository in the Kubernetes organization has beginner-friendly issues that provide a good first issue. For example, [kubernetes/kubernetes](https://git.k8s.io/kubernetes) has [help wanted issues](https://go.k8s.io/help-wanted) that should not need deep knowledge of the system. +Each repository in the Kubernetes organization has beginner-friendly issues that provide a good first issue. For example, [kubernetes/kubernetes](https://git.k8s.io/kubernetes) has [help wanted](https://go.k8s.io/help-wanted) and [good first issue](https://github.com/kubernetes/kubernetes/labels/good%20first%20issue) labels for issues that should not need deep knowledge of the system. +The `good first issue` label indicates that members have committed to providing extra assistance for new contributors. + Another good strategy is to find a documentation improvement, such as a missing/broken link, which will give you exposure to the code submission/review process without the added complication of technical depth. Please see [Contributing](#contributing) below for the workflow. ### Learn about SIGs |