SIG-Scheduling 2020 Annual Report #5557

Huang-Wei · 2021-02-24T19:26:40Z

Adding initial template for SIG-Scheduling 2020 Annual Report.

This is due by March 8th and will be shown to the SIG and Slack.

Which issue(s) this PR fixes:

k8s-ci-robot · 2021-02-24T19:26:41Z

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

k8s-ci-robot · 2021-02-24T19:26:52Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Huang-Wei

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~sig-scheduling/OWNERS~~ [Huang-Wei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Huang-Wei · 2021-02-24T19:28:44Z

Opened this as a placeholder, @ahg-g and I will fill out unanswered parts by this week.

/assign @liggitt

nikhita · 2021-02-25T11:13:58Z

/committee steering

ahg-g

some suggestions

sig-scheduling/2020-annual-report.md

ahg-g · 2021-02-25T17:07:15Z

/sig scheduling

Huang-Wei · 2021-02-26T02:49:52Z

@liggitt the first version is ready for review. Take your time.

sig-scheduling/2020-annual-report.md

parispittman · 2021-04-03T02:50:16Z

sig-scheduling/2020-annual-report.md

+
+Owners from (active) subprojects introduce the latest development, and sometime demonstrate
+cool features.
+OWNER files in k/k are not that up to date. We may need a cleanup.


is this something contribex can help with?

I think we are fine, we can send a PR to remove inactive members and tag them on that PR.

I suppose it's a common issue across all sigs. It'd be neat if we can come up with a script auto-identifying the inactive maintainers/reviewers:

for a particular SIG, not participated in any PR reviews in the last 12 (or 18) months

a single bare "/lgtm" or "/approve" doesn't count as a legal review

parispittman · 2021-04-03T02:51:12Z

sig-scheduling/2020-annual-report.md

+
+**Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?**
+
+Yes, except for inactive subprojects.


which ones are inactive?

kube-batch. The original plan is to develop batch-related features in a separate project, and eventually converge with default scheduler. But kube-batch is now incubated into a cncf sandobx project called volcano. So kube-batch is not active now.

poseidon. I don't see much interested in this project, and it's also no longer actively developed.

are those subprojects inactive to the point that their readme's should be updated to note that?

I will create issues in those subprojects to discuss what to do next: whether specify the inactive status in README, or just archive them.

Followup for:

kube-batch: Status of kube-batch kubernetes-retired/kube-batch#948

poseidon: Status of poseidon kubernetes-retired/poseidon#187

parispittman · 2021-04-03T02:52:01Z

sig-scheduling/2020-annual-report.md

+**How does the group measure reviewer and approver bandwidth? Do you need help in any area now?
+ What are you doing about it?**
+
+PRs are usually directed to the reviewer most familiar with the code base the PR is modifying.


are you growing more reviewers and approvers?

I think we have have enough approvals for the volume of the PRs we are getting, reviewers are growing.

Yes, we're fine by now.

parispittman · 2021-04-03T02:52:30Z

sig-scheduling/2020-annual-report.md

+activities that the group does to encourage this? What programs are you participating in to 
+grow contributors throughout the contributor ladder?**
+
+There is no official onboarding process. One thing we try to do frequently is breaking up 


Do you use help-wanted or good-first issue labels?

both depending on the complexity of the issue.

parispittman · 2021-04-03T02:53:07Z

sig-scheduling/2020-annual-report.md

+**Does the group have contributors from multiple companies/affiliations? Can end users/companies 
+contribute in some way that they currently are not?**
+
+Yes.


Do you want more companies to contribute? If so, to what and what extent? This is a microphone to end users

I don't think we are lacking diversity, there are 5+ companies involved in the sig on/off.

parispittman · 2021-04-03T02:54:03Z

sig-scheduling/2020-annual-report.md

+**What are initiatives that should be highlighted, lauded, shout out, that your group is proud of?
+ Currently underway? What are some of the longer tail projects that your group is working on?**
+
+- Initiatives:


ty for sectioning them out this way

parispittman · 2021-04-03T02:55:17Z

sig-scheduling/2020-annual-report.md

+
+**What areas and/or subprojects does the group need the most help with?**
+
+- **Docs improvement**:


ty for calling this out

agreed, thanks. I noticed https://docs.google.com/document/d/1t2QoASmg_BssFczl8n7UNTDWKgncMSrLTX802fQ0lK8/edit# and #5674 recently, which seemed to address some of the developer-facing bits. Would it make sense to open help-wanted issues for remaining dev doc gaps and for specific user-oriented gaps?

Yes, @ingvagabund 's recent contributions really make the docs greatly improved. With those docs in place, I think we're fine on dev docs. In terms of user-oriented doc gaps, we will open help-wanted issues for tracking.

dims · 2021-04-09T21:23:50Z

/committee steering

liggitt

lgtm, I just had one question about the two inactive subprojects mentioned

liggitt · 2021-04-13T01:19:24Z

sig-scheduling/2020-annual-report.md

+
+**What's the average open days of a PR and Issue in your group? What metrics does your group care about and/or measure?**
+
+We haven't stated leveraging devstat data or Github board to get a high-level picture of PR/Issue.


Suggested change

We haven't stated leveraging devstat data or Github board to get a high-level picture of PR/Issue.

We haven't started leveraging devstat data or Github board to get a high-level picture of PR/Issue.

liggitt · 2021-04-13T01:23:40Z

sig-scheduling/2020-annual-report.md

+
+**What areas and/or subprojects does the group need the most help with?**
+
+- **Docs improvement**:


agreed, thanks. I noticed https://docs.google.com/document/d/1t2QoASmg_BssFczl8n7UNTDWKgncMSrLTX802fQ0lK8/edit# and #5674 recently, which seemed to address some of the developer-facing bits. Would it make sense to open help-wanted issues for remaining dev doc gaps and for specific user-oriented gaps?

liggitt · 2021-04-13T18:23:39Z

/lgtm
with steering hat

/hold
for lgtm by sig-scheduling co-lead @ahg-g

ahg-g · 2021-04-13T18:25:16Z

/lgtm

liggitt · 2021-04-13T18:26:18Z

/hold cancel

k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 24, 2021

k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 24, 2021

k8s-ci-robot requested review from ahg-g and liggitt February 24, 2021 19:26

k8s-ci-robot assigned liggitt Feb 24, 2021

k8s-ci-robot added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Feb 25, 2021

ahg-g reviewed Feb 25, 2021

View reviewed changes

Huang-Wei force-pushed the sig-scheduling-2020-annual-report branch from 466fb62 to 04216b0 Compare February 26, 2021 02:48

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 26, 2021

Huang-Wei marked this pull request as ready for review February 26, 2021 02:49

k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 26, 2021

cofyc reviewed Mar 2, 2021

View reviewed changes

sig-scheduling/2020-annual-report.md Show resolved Hide resolved

Huang-Wei force-pushed the sig-scheduling-2020-annual-report branch from 04216b0 to 1f25fd6 Compare March 2, 2021 20:50

parispittman suggested changes Apr 3, 2021

View reviewed changes

liggitt reviewed Apr 13, 2021

View reviewed changes

SIG-Scheduling 2020 Annual Report

0b47ff0

Huang-Wei force-pushed the sig-scheduling-2020-annual-report branch from 1f25fd6 to 0b47ff0 Compare April 13, 2021 17:35

k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 13, 2021

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 13, 2021

k8s-ci-robot assigned ahg-g Apr 13, 2021

k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 13, 2021

k8s-ci-robot merged commit af45c14 into kubernetes:master Apr 13, 2021

Huang-Wei deleted the sig-scheduling-2020-annual-report branch April 13, 2021 18:50

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SIG-Scheduling 2020 Annual Report #5557

SIG-Scheduling 2020 Annual Report #5557

Huang-Wei commented Feb 24, 2021

k8s-ci-robot commented Feb 24, 2021

k8s-ci-robot commented Feb 24, 2021

Huang-Wei commented Feb 24, 2021

nikhita commented Feb 25, 2021

ahg-g left a comment

ahg-g commented Feb 25, 2021

Huang-Wei commented Feb 26, 2021

parispittman Apr 3, 2021

ahg-g Apr 5, 2021

Huang-Wei Apr 5, 2021

lilinji Aug 25, 2021

parispittman Apr 3, 2021

Huang-Wei Apr 5, 2021

liggitt Apr 13, 2021

Huang-Wei Apr 13, 2021

Huang-Wei Apr 13, 2021

parispittman Apr 3, 2021

ahg-g Apr 5, 2021

Huang-Wei Apr 5, 2021

parispittman Apr 3, 2021

ahg-g Apr 5, 2021

parispittman Apr 3, 2021

ahg-g Apr 5, 2021

parispittman Apr 3, 2021

parispittman Apr 3, 2021

liggitt Apr 13, 2021

Huang-Wei Apr 13, 2021

dims commented Apr 9, 2021

liggitt left a comment

liggitt Apr 13, 2021

liggitt Apr 13, 2021

liggitt commented Apr 13, 2021

ahg-g commented Apr 13, 2021

liggitt commented Apr 13, 2021


		Are all listed SIG leaders (chairs, tech leads, and subproject owners) active?

		Yes, except for inactive subprojects.


		What areas and/or subprojects does the group need the most help with?

		- Docs improvement:


		What's the average open days of a PR and Issue in your group? What metrics does your group care about and/or measure?

		We haven't stated leveraging devstat data or Github board to get a high-level picture of PR/Issue.

	We haven't stated leveraging devstat data or Github board to get a high-level picture of PR/Issue.
	We haven't started leveraging devstat data or Github board to get a high-level picture of PR/Issue.

SIG-Scheduling 2020 Annual Report #5557

SIG-Scheduling 2020 Annual Report #5557

Conversation

Huang-Wei commented Feb 24, 2021

k8s-ci-robot commented Feb 24, 2021

k8s-ci-robot commented Feb 24, 2021

Huang-Wei commented Feb 24, 2021

nikhita commented Feb 25, 2021

ahg-g left a comment

Choose a reason for hiding this comment

ahg-g commented Feb 25, 2021

Huang-Wei commented Feb 26, 2021

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dims commented Apr 9, 2021

liggitt left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

liggitt commented Apr 13, 2021

ahg-g commented Apr 13, 2021

liggitt commented Apr 13, 2021