|
4 | 4 |
|
5 | 5 | 1. What work did the SIG do this year that should be highlighted?
|
6 | 6 |
|
7 |
| - - |
8 |
| - - |
9 |
| - - |
| 7 | + - Improvements to PodTopologySpread API: adding more knobs to control spreading behavior (introducing minDomains and matchLabelKey). |
| 8 | + - Adding more hooks to simplify integrations with external schedulers (mutable pod scheduling directives, pod scheduling readiness) |
| 9 | + |
10 | 10 |
|
11 | 11 | 2. What initiatives are you working on that aren't being tracked in KEPs?
|
12 | 12 |
|
13 |
| - - |
14 |
| - - |
15 |
| - - |
| 13 | + - Performance improvements |
| 14 | + - Code refactorings and cleanups |
| 15 | + |
16 | 16 |
|
17 | 17 |
|
18 | 18 |
|
|
39 | 39 |
|
40 | 40 | 2. What metrics/community health stats does your group care about and/or measure?
|
41 | 41 |
|
42 |
| - - |
43 |
| - - |
44 |
| - - |
| 42 | + - Diversity |
| 43 | + - Number of contributors |
| 44 | + - Meetings attendance |
45 | 45 |
|
46 | 46 | 3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
|
47 | 47 | to activities or programs that provide useful context or allow easy participation?
|
48 | 48 |
|
49 |
| - - |
| 49 | + - It looks up-to-date |
50 | 50 |
|
51 | 51 | 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
|
52 | 52 | does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
|
53 | 53 |
|
54 |
| - - |
| 54 | + - Nothing special |
55 | 55 |
|
56 | 56 | 5. Does the group have contributors from multiple companies/affiliations?
|
57 | 57 |
|
58 |
| - - |
| 58 | + - Yes |
59 | 59 |
|
60 | 60 | 6. Are there ways end users/companies can contribute that they currently are not?
|
61 | 61 | If one of those ways is more full time support, what would they work on and why?
|
|
65 | 65 |
|
66 | 66 | ## Membership
|
67 | 67 |
|
68 |
| -- Primary slack channel member count: |
69 |
| -- Primary mailing list member count: |
70 |
| -- Primary meeting attendee count (estimated, if needed): |
71 |
| -- Primary meeting participant count (estimated, if needed): |
72 |
| -- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
73 |
| -- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
| 68 | +- Primary slack channel member count: 3050 |
| 69 | +- Primary mailing list member count: 655 |
| 70 | +- Primary meeting attendee count (estimated, if needed): 10 |
| 71 | +- Primary meeting participant count (estimated, if needed): 5 |
| 72 | +- Unique reviewers for SIG-owned packages: 6 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
| 73 | +- Unique approvers for SIG-owned packages: 4 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> |
74 | 74 |
|
75 | 75 | Include any other ways you measure group membership
|
76 | 76 |
|
@@ -114,16 +114,17 @@ Include any other ways you measure group membership
|
114 | 114 |
|
115 | 115 | Operational tasks in [sig-governance.md]:
|
116 | 116 |
|
117 |
| -- [ ] [README.md] reviewed for accuracy and updated if needed |
118 |
| -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
| 117 | +- [x] [README.md] reviewed for accuracy and updated if needed |
| 118 | +- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed |
119 | 119 | (or created if missing and your contributor steps and experience are different or more
|
120 | 120 | in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
|
121 |
| -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
122 |
| -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
123 |
| -- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
124 |
| -- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
125 |
| - - |
126 |
| - - |
| 121 | +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed |
| 122 | +- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed |
| 123 | +- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed |
| 124 | +- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: |
| 125 | + - [2022 KubeCon NA: SIG-Scheduling Intro & Deep Dive](https://www.youtube.com/watch?v=1GpTE9L9oBM) |
| 126 | + - [2022 KubeCon EU: SIG-Scheduling Intro & Deep Dive](https://www.youtube.com/watch?v=R2CpmLfHUYk) |
| 127 | + - |
127 | 128 |
|
128 | 129 | [CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
|
129 | 130 | [contributor ladder]: https://git.k8s.io/community/community-membership.md
|
|
0 commit comments