From 888900324f0f2d83e2b004bc5e4581b1b98e1727 Mon Sep 17 00:00:00 2001 From: divya-mohan0209 Date: Thu, 24 Feb 2022 09:48:00 +0530 Subject: [PATCH] Update sig-docs/annual-report-2021.md Co-authored-by: Paris --- sig-docs/annual-report-2021.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-docs/annual-report-2021.md b/sig-docs/annual-report-2021.md index e105941d3..2ad1d3641 100644 --- a/sig-docs/annual-report-2021.md +++ b/sig-docs/annual-report-2021.md @@ -50,7 +50,7 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? - - We have a [well-documented guide](https://kubernetes.io/docs/contribute/#:~:text=Anyone%20can%20open%20an%20issue,the%20CNCF%20Contributor%20License%20Agreement.) that details how folks can get started and the various ways in which they can scale the contributor ladder. + - We have a [well-documented guide](https://kubernetes.io/docs/contribute/) that details how folks can get started and the various ways in which they can scale the contributor ladder. - We actively assign good-first-issue labels to issues that we think early-lifecycle contributors could begin with. During KubeCons we also do introduction presentations and mentoring sessions to try and funnel contributors in to our SIG. 5. Does the group have contributors from multiple companies/affiliations?