Merge pull request #7215 from ahg-g/master
sig-scheduling annual report
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
52142f3967
|
|
@ -4,15 +4,17 @@
|
|||
|
||||
1. What work did the SIG do this year that should be highlighted?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- Improvements to PodTopologySpread API: adding more knobs to control spreading behavior (introducing minDomains and matchLabelKey).
|
||||
- Adding more hooks to simplify integrations with external schedulers (mutable pod scheduling directives, pod scheduling readiness)
|
||||
|
||||
|
||||
2. What initiatives are you working on that aren't being tracked in KEPs?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- Performance improvements.
|
||||
- Code refactorings and cleanups.
|
||||
- [Kueue](https://kueue.sigs.k8s.io/), a k8s-native job scheduling and queueing controller, a new subproject sponsored by the sig.
|
||||
- [scheduler-plugins](https://sigs.k8s.io/scheduler-plugins), repository for out-of-tree scheduler plugins.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -33,29 +35,29 @@
|
|||
1. What areas and/or subprojects does your group need the most help with?
|
||||
Any areas with 2 or fewer OWNERs? (link to more details)
|
||||
|
||||
-
|
||||
- Increase the number of reviewers ([call for reviewers](https://groups.google.com/g/kubernetes-sig-scheduling/c/ZzxAujy6dLM))
|
||||
-
|
||||
-
|
||||
|
||||
2. What metrics/community health stats does your group care about and/or measure?
|
||||
|
||||
-
|
||||
-
|
||||
-
|
||||
- Diversity
|
||||
- Number of contributors
|
||||
- Meetings attendance
|
||||
|
||||
3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing
|
||||
to activities or programs that provide useful context or allow easy participation?
|
||||
|
||||
-
|
||||
- It looks up-to-date
|
||||
|
||||
4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide],
|
||||
does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]?
|
||||
|
||||
-
|
||||
- Nothing special
|
||||
|
||||
5. Does the group have contributors from multiple companies/affiliations?
|
||||
|
||||
-
|
||||
- Yes
|
||||
|
||||
6. Are there ways end users/companies can contribute that they currently are not?
|
||||
If one of those ways is more full time support, what would they work on and why?
|
||||
|
|
@ -65,12 +67,12 @@
|
|||
|
||||
## Membership
|
||||
|
||||
- Primary slack channel member count:
|
||||
- Primary mailing list member count:
|
||||
- Primary meeting attendee count (estimated, if needed):
|
||||
- Primary meeting participant count (estimated, if needed):
|
||||
- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
|
||||
- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
|
||||
- Primary slack channel member count: 3050
|
||||
- Primary mailing list member count: 655
|
||||
- Primary meeting attendee count (estimated, if needed): 10
|
||||
- Primary meeting participant count (estimated, if needed): 5
|
||||
- Unique reviewers for SIG-owned packages: 6 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
|
||||
- Unique approvers for SIG-owned packages: 4 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files -->
|
||||
|
||||
Include any other ways you measure group membership
|
||||
|
||||
|
|
@ -114,16 +116,17 @@ Include any other ways you measure group membership
|
|||
|
||||
Operational tasks in [sig-governance.md]:
|
||||
|
||||
- [ ] [README.md] reviewed for accuracy and updated if needed
|
||||
- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
|
||||
- [x] [README.md] reviewed for accuracy and updated if needed
|
||||
- [x] [CONTRIBUTING.md] reviewed for accuracy and updated if needed
|
||||
(or created if missing and your contributor steps and experience are different or more
|
||||
in-depth than the documentation listed in the general [contributor guide] and [devel] folder.)
|
||||
- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
|
||||
- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
|
||||
- [ ] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
|
||||
- [ ] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
|
||||
-
|
||||
-
|
||||
- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
|
||||
- [x] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed
|
||||
- [x] Meeting notes and recordings for 2022 are linked from [README.md] and updated/uploaded if needed
|
||||
- [x] Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings:
|
||||
- [2022 KubeCon NA: SIG-Scheduling Intro & Deep Dive](https://www.youtube.com/watch?v=1GpTE9L9oBM)
|
||||
- [2022 KubeCon EU: SIG-Scheduling Intro & Deep Dive](https://www.youtube.com/watch?v=R2CpmLfHUYk)
|
||||
-
|
||||
|
||||
[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
|
||||
[contributor ladder]: https://git.k8s.io/community/community-membership.md
|
||||
|
|
|
|||
Loading…
Reference in New Issue