Skip to content

Commit 242a0d5

Browse files
committed
sig-scheduling annual report
1 parent 11eebf6 commit 242a0d5

File tree

1 file changed

+27
-26
lines changed

1 file changed

+27
-26
lines changed

sig-scheduling/annual-report-2022.md

Lines changed: 27 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -4,15 +4,15 @@
44

55
1. What work did the SIG do this year that should be highlighted?
66

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+
1010

1111
2. What initiatives are you working on that aren't being tracked in KEPs?
1212

13-
-
14-
-
15-
-
13+
- Performance improvements
14+
- Code refactorings and cleanups
15+
1616

1717

1818

@@ -39,23 +39,23 @@
3939

4040
2. What metrics/community health stats does your group care about and/or measure?
4141

42-
-
43-
-
44-
-
42+
- Diversity
43+
- Number of contributors
44+
- Meetings attendance
4545

4646
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
4747
to activities or programs that provide useful context or allow easy participation?
4848

49-
-
49+
- It looks up-to-date
5050

5151
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
5252
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
5353

54-
-
54+
- Nothing special
5555

5656
5. Does the group have contributors from multiple companies/affiliations?
5757

58-
-
58+
- Yes
5959

6060
6. Are there ways end users/companies can contribute that they currently are not?
6161
If one of those ways is more full time support, what would they work on and why?
@@ -65,12 +65,12 @@
6565

6666
## Membership
6767

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 -->
7474

7575
Include any other ways you measure group membership
7676

@@ -114,16 +114,17 @@ Include any other ways you measure group membership
114114

115115
Operational tasks in [sig-governance.md]:
116116

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
119119
(or created if missing and your contributor steps and experience are different or more
120120
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+
-
127128

128129
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
129130
[contributor ladder]: https://git.k8s.io/community/community-membership.md

0 commit comments

Comments
 (0)