Skip to content

sig-scheduling annual report #7215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 13, 2023
Merged

sig-scheduling annual report #7215

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
242a0d5
sig-scheduling annual report
ahg-g Mar 24, 2023
18993ca
addressed comments
ahg-g Apr 13, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
57 changes: 30 additions & 27 deletions sig-scheduling/annual-report-2022.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.




Expand All @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While we are doing well in the nationality/ethnicity front, we are not doing well in gender diversity. Not really sure how to improve this.

- 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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems we have no CONTRIBUTING.md to sig-scheduling specifically. It's empty.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can draft one, I recalled we got a developer from the community who asked for the same question about how to learn kube-scheduler in the community meeting.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't find the thread, but I remember the guidance was that if we don't have any special training or requirements beyond https://git.k8s.io/community/community-membership.md, we don't need this page.

This is not the same as developer documentations, which can be found in https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scheduling

One thing I can think of, but it's not 100% enforced: each PR needs first an LGTM from a reviewer before getting approval.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A developer document could also be part of the CONTRIBUTING.md, I found some sigs have self-owned ones, like the sig-apps, sig-node, but it's not strict.

Anyway, I can draft one later.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#7228


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?
Expand All @@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

em.. one thing I think related here is the APAC meeting, usually hosted by @Huang-Wei ❤️
but we have very little attendees each time. 🤷‍♂️ but I think we can still move on if we have agenda. FYI.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The APAC meeting doesn't run smoothly atm. We don't have concrete agenda items and less attendees than expected. TBH I'm considering closing it sometime in the future.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this grows the burden for you can't just ignore it, but another problem is the primary sig scheduling meeting is usually too late for APAC, 12 am or 1 am in the midnight, I admit I have selfishness here. 😄

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Negotiating a meeting time across the globe is always challenging :(

@alculquicondor @ahg-g what's your take?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should go back to alternated times, preserving meetings every 2 weeks.

We have 3 TLs, two in PDT and one in EDT. Ideally each meeting should fall within business hours of at least two TLs. The current one falls within business hours of all of us. I think we can keep this one and move the other one, but I think it will still have to be slightly out of business hours.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I admit I have selfishness here.

Not at all, we should accommodate for as many contributors as possible.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have 3 TLs, two in PDT and one in EDT. Ideally each meeting should fall within business hours of at least two TLs. The current one falls within business hours of all of us. I think we can keep this one and move the other one, but I think it will still have to be slightly out of business hours.

It would be nice to have this. 😄

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess nothing to add to the report with regards to this thread, please let me know if not

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kerthcet can you create an issue for this in this repo?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #7254

- 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

Expand Down Expand Up @@ -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
Expand Down