You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sig-docs/annual-report-2021.md
+41-71Lines changed: 41 additions & 71 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,79 +4,72 @@
4
4
5
5
1. What work did the SIG do this year that should be highlighted?
6
6
7
-
-
8
-
-
9
-
-
7
+
- SIG Docs put meaningful effort into growing its contributor and reviewer base in 2021, introducing a shadow program for PR Wrangling as well as dedicating more time to being active via our Slack community channel. This is an ongoing effort to grow our contributor base to a stable number, alongside easing the burden on our small group of reviewers and approvers.
8
+
- Alongside growing our contributor base, SIG Docs also worked on a leadership transition strategy to bring community members into leadership roles. Via a specialized six month mentorship program expertly led by Steering Committee member Paris Pittman, SIG Docs was able to grow its leadership cohort for the main SIG, as well as some of its subgroups, adding new co-chairs and tech leads.
10
9
11
10
2. What initiatives are you working on that aren't being tracked in KEPs?
12
11
13
-
-
14
-
-
15
-
-
12
+
- Localization Subproject: SIG Docs is working on formalizing the localization work that has been ongoing for some time, with appointed leads of this initiative as well as recognizing the contributions of various community members across the different languages the Kubernetes website has been translated into. This subproject will be finalized by Q1 2022, with all active localizations informed and updated.
13
+
- New Contributor Ambassador Program: As a continuation of our push to grow the SIG Docs contributor base, we're working on a specalized role that aims to support new and would-be contributors get up to speed with our processes and workflows. This role would be capped at six months for it to be shared amongst the community, with this feeding into a possible reviewer funnel as contributors get more comfortable with providing feedback to others.
16
14
17
-
3. KEP work in 2021 (1.x, 1.y, 1.z):
15
+
3. KEP work in 2021 (continuous and does not target any release):
18
16
19
17
<!--
20
18
In future, this will be generated from kubernetes/enhancements kep.yaml files
21
19
1. with SIG as owning-sig or in participating-sigs
22
20
2. listing 1.x, 1.y, or 1.z in milestones or in latest-milestone
-[1326 - Doc policies for third party content](https://git.k8s.io/enhancements/keps/sig-docs/1326-third-party-content-in-docs/README.md)
24
+
36
25
37
26
## Project health
38
27
39
28
1. What areas and/or subprojects does your group need the most help with?
40
29
Any areas with 2 or fewer OWNERs? (link to more details)
41
30
42
-
-
43
-
-
44
-
-
31
+
- Require more contributors to form a stable pool for SIG Docs
32
+
- Require guidelines on how we could ramp up folks nominated to the New Contributor Ambassador role specific to SIG Docs.
45
33
46
34
2. What metrics/community health stats does your group care about and/or measure?
47
35
48
-
-
49
-
-
50
-
-
36
+
37
+
- SIG Docs has a [dashboard](https://datastudio.google.com/u/0/reporting/fede2672-b2fd-402a-91d2-7473bdb10f04/page/567IC) available with site anyaltics. Some highlights include:
- PR velocity and open PR age is tracked in [Devstat](https://k8s.devstats.cncf.io/d/25/open-pr-age-by-repository-group?orgId=1&var-period=q&var-repogroup_name=SIG%20Docs&var-kind_name=All). We aim to have < 100 open PRs for the English localization, and will take steps as needed if we see the figure climbing much above that. For example, based on 12/31/2020 data, we have: Average number of opened PRs 368 with the median opened PRs age 5 days 21 hours 26 minutes 42 seconds
51
44
52
45
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
46
to activities or programs that provide useful context or allow easy participation?
54
47
55
-
-
48
+
- It's updated to the best of our knowledge.
56
49
57
50
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
51
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
52
60
-
-
53
+
- 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.
54
+
- 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.
61
55
62
56
5. Does the group have contributors from multiple companies/affiliations?
6. Are there ways end users/companies can contribute that they currently are not?
67
61
If one of those ways is more full time support, what would they work on and why?
68
62
69
-
-
70
-
-
63
+
- We're in the process of formalizing the localization subproject. We aim for it to, potentially, provide more avenues for contribution. More details around leadership for the localization supbproject can be found in [this message](https://groups.google.com/a/kubernetes.io/g/dev/c/SP6weMvx3wg/m/l8LAL-OFCQAJ) sent to [email protected]
71
64
72
65
## Membership
73
66
74
-
- Primary slack channel member count:
75
-
- Primary mailing list member count:
76
-
- Primary meeting attendee count (estimated, if needed):
77
-
- Primary meeting participant count (estimated, if needed):
78
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
67
+
- Primary slack channel member count: 1876
68
+
- Primary mailing list member count: 453
69
+
- Primary meeting attendee count (estimated, if needed): 10
70
+
- Primary meeting participant count (estimated, if needed): 6
71
+
- Unique reviewers for SIG-owned packages: 76 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
72
+
- Unique approvers for SIG-owned packages: 93<!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
73
81
74
Include any other ways you measure group membership
82
75
@@ -87,51 +80,28 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
80
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
In 2021, SIG Docs started to formalize the localization subgroup into an official subproject.
120
89
121
90
## Operational
122
91
123
92
Operational tasks in [sig-governance.md]:
124
93
125
-
-[][README.md] reviewed for accuracy and updated if needed
126
-
-[][CONTRIBUTING.md] reviewed for accuracy and updated if needed
94
+
-[x][README.md] reviewed for accuracy and updated if needed
95
+
-[X][CONTRIBUTING.md] reviewed for accuracy and updated if needed
127
96
(or created if missing and your contributor steps and experience are different or more
128
97
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
129
-
-[ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
130
-
-[ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
131
-
-[ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
132
-
-[ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
133
-
-
134
-
-
98
+
-[X] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
99
+
-[X] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
100
+
-[x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
101
+
-[x] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
102
+
- [Kubernetes SIG Docs: A Deep Dive](https://www.youtube.com/watch?v=GDfcBF5et3Q), presented at KubeCon NA, 2021
103
+
- [SIG Docs: New roles & leadership nominations to [email protected]](https://groups.google.com/a/kubernetes.io/g/dev/c/SP6weMvx3wg/m/l8LAL-OFCQAJ)
104
+
- [SIG Docs APAC Meeting has changed to 1 AM IST/5.30 AM UTC on the last Wednesday of every month to [email protected]](https://groups.google.com/g/kubernetes-sig-docs/c/P7iLejmEIFA/m/-dPsBOpoDAAJ)
0 commit comments