diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-06-12 11:38:28 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-12 11:38:28 -0700 |
| commit | 8a4383f12e1e43d774cfa11629a48f1f276e82e3 (patch) | |
| tree | a9d0c9bfd9a654df318bfb9f89517af8ff235193 | |
| parent | 0166571bce74e0c465b3d68c4a1121a2ca41025a (diff) | |
| parent | 6d3c337df3ea6f71cc5a536523a25c8afbc7d7d2 (diff) | |
Merge pull request #2252 from clandry94/good_first_issue_addendum
add a notice that the good first issue label is new and a WIP
| -rw-r--r-- | contributors/guide/README.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index d2540117..d2027344 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -74,6 +74,8 @@ You get the idea - if you ever see something you think should be fixed, you shou 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](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. +<!-- TODO: review removing this note after 3 months or after the 1.12 release --> +Please note that while several of the repositories in the Kubernetes community have `good first issue` labels already, they are still being applied throughout the community. 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. |