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
-[1040 - Priority and Fairness for API Server Requests](https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1040-priority-and-fairness/README.md) - 1.23
1. What areas and/or subprojects does your group need the most help with?
40
32
Any areas with 2 or fewer OWNERs? (link to more details)
41
33
42
-
-
43
-
-
44
-
-
34
+
- Each subproject could benefit from additional hands. However, the Scalability Test Frameworks and Scalability and Performance tests and validation are the ones where we can grow contributors - the other require both very deep and wide understanding of Kubernetes before making reasonable contributions.
45
35
46
36
2. What metrics/community health stats does your group care about and/or measure?
47
37
48
-
-
49
-
-
50
-
-
38
+
- We care mostly about metrics for our main repository [perf-tests]. We measure them through [devstats]. We keep track of number of reviewers, opened issues and PRs merged.
51
39
52
40
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
53
41
to activities or programs that provide useful context or allow easy participation?
54
42
55
-
-
43
+
- Yes, [CONTRIBUTING.md] points to maintained list of issues with label `good first issue`.
56
44
57
45
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
58
46
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
59
47
60
-
-
48
+
- We don't have any special requirements for reviewers/approvers, but most of core areas of sig-scalability required deep and wide understanding of Kubernetes.
61
49
62
50
5. Does the group have contributors from multiple companies/affiliations?
63
51
64
-
-
52
+
- Yes, we have contributors from [multiple companies](https://k8s.devstats.cncf.io/d/8/company-statistics-by-repository-group?orgId=1&var-period=d7&var-metric=contributions&var-repogroup_name=SIG%20Scalability&var-repo_name=kubernetes%2Fkubernetes&var-companies=All&from=1609477200000&to=1640926800000).
65
53
66
54
6. Are there ways end users/companies can contribute that they currently are not?
67
55
If one of those ways is more full time support, what would they work on and why?
68
56
69
-
-
70
-
-
57
+
- End users usually come with questions about scalability, they rarely want to contribute.
71
58
72
59
## Membership
73
60
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 -->
61
+
- Primary slack channel member count: 2029
62
+
- Primary mailing list member count: 236
63
+
- Primary meeting attendee count (estimated, if needed): 5
64
+
- Primary meeting participant count (estimated, if needed): 4
65
+
- Unique reviewers for SIG-owned packages: 6
66
+
- Unique approvers for SIG-owned packages: 5
80
67
81
68
Include any other ways you measure group membership
82
69
@@ -87,17 +74,18 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y
87
74
Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md`
0 commit comments