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.24, 1.25, 1.26
1. What areas and/or subprojects does your group need the most help with?
25
39
Any areas with 2 or fewer OWNERs? (link to more details)
26
40
27
-
-
28
-
-
29
-
-
41
+
- Each SIG Scalability subproject could benefit from additional hands.
42
+
However, the Scalability Test Frameworks and Scalability and Performance tests and validation
43
+
are the ones with the lower barier to entry - see [perf-tests] repository.
44
+
Other areas require both very deep and wide understanding of Kubernetes before making reasonable contributions.
30
45
31
46
2. What metrics/community health stats does your group care about and/or measure?
32
47
33
-
-
34
-
-
35
-
-
48
+
- 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.
36
49
37
50
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
38
51
to activities or programs that provide useful context or allow easy participation?
39
52
40
-
-
53
+
- Yes, [CONTRIBUTING.md] points to maintained list of issues with label `good first issue`.
41
54
42
55
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
43
56
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
44
57
45
-
-
58
+
- We don't have any special requirements for reviewers/approvers, but most of core areas of sig-scalability require
59
+
very deep and wide understanding of the whole Kubernetes. It is much easier to start with our testing infrastructure.
46
60
47
61
5. Does the group have contributors from multiple companies/affiliations?
48
62
49
-
-
63
+
- 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=1641013200000&to=1672462800000).
50
64
51
65
6. Are there ways end users/companies can contribute that they currently are not?
52
66
If one of those ways is more full time support, what would they work on and why?
53
67
54
-
-
55
-
-
68
+
- End users usually come with questions about scalability, they rarely want to contribute.
69
+
- End user could also help us by providing and documenting their scalability needs to help us
70
+
better define our goals.
56
71
57
72
## Membership
58
73
59
-
- Primary slack channel member count:
60
-
- Primary mailing list member count:
61
-
- Primary meeting attendee count (estimated, if needed):
62
-
- Primary meeting participant count (estimated, if needed):
63
-
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
64
-
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
74
+
- Primary slack channel member count: 2299
75
+
- Primary mailing list member count: 260
76
+
- Primary meeting attendee count (estimated, if needed): 7
77
+
- Primary meeting participant count (estimated, if needed): 5
78
+
- Unique reviewers for SIG-owned packages: 6
79
+
- Unique approvers for SIG-owned packages: 5
65
80
66
81
Include any other ways you measure group membership
0 commit comments