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
2. What metrics/community health stats does your group care about and/or measure?
47
74
48
-
-
49
-
-
50
-
-
75
+
- We started collecting metrics from all of our subprojects using an
76
+
[yearly survey](https://forms.gle/xZn8DXww4XxPsXvCA). It contains a number of questions
77
+
related to project health, OWNERS files, contributor onboarding, etc. What we saw for this annual
78
+
report is that our OWNERS files and SIG README.md are mostly up-to-date and that subprojects are doing
79
+
what they can to onboard new contributors. We are considering preparing some actions to better educate
80
+
our subprojects about onboarding contributors and graduating more OWNERS.
51
81
52
82
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
83
to activities or programs that provide useful context or allow easy participation?
54
84
55
-
-
85
+
- As per the survey, we are seeing a good number of projects to keep their contributing
86
+
documentation up-to-date. We are drafting action items for the leads to improve the understanding
87
+
around [CONTRIBUTING.md] management. We have a good number of projects that have participated in LFX and GSoC.
56
88
57
89
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
90
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
91
60
-
-
92
+
- Our subprojects have implemented their own contributing process and they have their own criteria
93
+
for contributors to climb the ladders. We have not seen complains from new or existing
94
+
contributors related to contributor guides. The SIG leads are open to help subproject leads with tips
95
+
on this topic.
61
96
62
97
5. Does the group have contributors from multiple companies/affiliations?
63
98
64
-
-
99
+
- Yes, as confirmed by our survey.
65
100
66
101
6. Are there ways end users/companies can contribute that they currently are not?
67
102
If one of those ways is more full time support, what would they work on and why?
68
103
69
-
-
70
-
-
104
+
In our survey results we found a few common areas where more help is needed across subprojects:
105
+
- Code review
106
+
- CI / e2e test monitoring and integration
107
+
- Roadmap planning
108
+
- Docs authoring and review
109
+
110
+
These areas seems suitable for both full time and part time contributors.
111
+
Replying to user questions on Slack and other communication channels is something
112
+
that can be considered as full time support.
113
+
Users/companies can reach out to the subproject leads if certain details
114
+
are missing in the [CONTRIBUTING.md] file of a subproject.
71
115
72
116
## Membership
73
117
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 -->
118
+
- Primary slack channel member count: 2868
119
+
- Primary mailing list member count: 1157
120
+
- Primary meeting attendee count (estimated, if needed): 5-10
121
+
- Primary meeting participant count (estimated, if needed): 5-10
122
+
- Unique reviewers for SIG-owned packages: 30+ <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
123
+
- Unique approvers for SIG-owned packages: 30+ <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
124
81
125
Include any other ways you measure group membership
82
126
127
+
We do not count the overall group members because we have
-[][README.md] reviewed for accuracy and updated if needed
126
-
-[][CONTRIBUTING.md] reviewed for accuracy and updated if needed
169
+
-[x][README.md] reviewed for accuracy and updated if needed
170
+
-[x][CONTRIBUTING.md] reviewed for accuracy and updated if needed
127
171
(or created if missing and your contributor steps and experience are different or more
128
172
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
129
173
-[ ] 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
-
-
174
+
-[x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
175
+
-[x] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed
176
+
-[x] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
177
+
- [Vince Prignano became a SIG chair, Timothy St. Clair moved to emeritus](https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/LDF5udJnrzI/m/d5THJ-lsAAAJ)
0 commit comments