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
@@ -38,43 +40,60 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files
38
40
39
41
1. What areas and/or subprojects does your group need the most help with?
40
42
Any areas with 2 or fewer OWNERs? (link to more details)
43
+
44
+
The SIG sponsors some working groups that are largely independent.
45
+
46
+
There are several areas where regularly the SIG becomes under pressure, especially closer to code freezes and the
47
+
vast amount of code owned by API Machinery.
41
48
42
-
-
43
-
-
44
-
-
49
+
The ecosystem of the different Kubernetes Clients that we own grows more or less organically. Client-go and
50
+
Python-client are probably the bigger ones.
51
+
52
+
There are some packages that API Machinery owns and come out usually in our triage meetings, and that we most likely
53
+
don't know much about: this happens often when Kubernetes is upgrading libraries for example.
54
+
55
+
Technical support for triages could have improvements, for example sometimes we remove API Machinery in PRs, and every update to the issue / pr get's us re- tagged again.
45
56
46
57
2. What metrics/community health stats does your group care about and/or measure?
47
58
48
-
-
49
-
-
50
-
-
59
+
On the technical health of the SIG, we look at
60
+
- the ratio of open/close PRs
61
+
- the ratio of open/close Issues
62
+
- overall age of open Issues
63
+
- Number of active contributors to the sig
64
+
65
+
On the inclusion health of the SIG, we look at:
66
+
- representation of diversity and of multiple companies in the sig participants
51
67
52
68
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
69
to activities or programs that provide useful context or allow easy participation?
54
70
55
-
-
71
+
- No, it can be improved. Usually we find many contributors via slack, PRs, and issues.
72
+
56
73
57
74
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
75
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
76
60
-
-
77
+
- No, it can be improved. The main concern has always been the large amount of investment that is required to ramp up new contributors
61
78
62
79
5. Does the group have contributors from multiple companies/affiliations?
63
80
64
-
-
65
-
81
+
Yes, there are contributors from [multiple companies](https://k8s.devstats.cncf.io/d/74/contributions-chart?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20API%20Machinery&var-country_name=All&var-company_name=All&var-company=all).
82
+
We see all sorts of contributions, varying from issues, to comments, to PRs, to designs, to sig meeting participation,
83
+
and user-survey data.
84
+
66
85
6. Are there ways end users/companies can contribute that they currently are not?
67
86
If one of those ways is more full time support, what would they work on and why?
68
87
69
-
-
70
-
-
88
+
- This is a topic that appears frequently. API Machinery owns ~40% of the Kubernetes code base. In the past, we had some newcomers show up in SIG meetings with very concrete support questions. This is not the right forum, and that is not what we want to turn those meetings into.
89
+
- There is plenty of areas were the SIG could use help in reviewing and maintaining the code, but it's a complicated code base to ramp up. If people don't stick around long enough, the effort does not make sense.
71
90
72
91
## Membership
73
92
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):
93
+
- Primary slack channel member count: 3,384
94
+
- Primary mailing list member count: 689
95
+
- Primary meeting attendee count (estimated, if needed): 30
96
+
- Primary meeting participant count (estimated, if needed): 10
78
97
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
79
98
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
80
99
@@ -87,17 +106,93 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
106
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments