Skip to content
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.

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

a new sig-scheduling meeting friendly for Asia/Europe #8299

Open
sanposhiho opened this issue Jan 26, 2025 · 10 comments
Open

a new sig-scheduling meeting friendly for Asia/Europe #8299

sanposhiho opened this issue Jan 26, 2025 · 10 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@sanposhiho
Copy link
Member

sanposhiho commented Jan 26, 2025

What

SIG-Scheduling has a biweekly meeting on Thursdays at 17:00 UTC, which is late especially for Asia maintainers.
This issue proposes adding another regular sig meeting at Asia/Europe friendly time slot.

Why

Looking at @kubernetes/sig-scheduling-misc, other subprojects' core maintainers (e.g., @tenzen-y, @wzshiming, etc etc), and other contributors not listed there too, Asia power is indispensable for the team like other regions 🙂

Context

We had an APAC sig meeting before (ref), but we stopped it due to the inactivity (ref).

I can talk only about the situation at k/k though, it's been changing especially after we've got @macsko and @dom4ha.
Recently many discussions have been driven by me, @macsko, and @dom4ha; it could probably be sometimes easier for us to discuss things directly at the meetings. So, that's where the motivation to revive the asia sig meetings arose from.

/kind documentation
/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 26, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@sanposhiho
Copy link
Member Author

@sanposhiho
Copy link
Member Author

/assign

I'll make a poll to decide the schedule. Frequency-wise, I'm thinking of scheduling it bi-weekly (and skip the one if no agenda), but I'm open to the discussion.

@sanposhiho
Copy link
Member Author

Created the poll: https://doodle.com/meeting/organize/id/en7o2G7a

@dom4ha
Copy link
Member

dom4ha commented Jan 26, 2025

Thank you Kensei. I left my vote and bi-weekly schedule should be fine.

@jpedro1992
Copy link

This is a very good idea! It is often challenging for me to attend the sig-scheduling meetings regularly since I am located in Europe.

@alculquicondor
Copy link
Member

/migrate community
(Not sure if this was the command)

@alculquicondor
Copy link
Member

/transfer community
found it

@github-project-automation github-project-automation bot moved this to Needs Triage in SIG Scheduling Jan 27, 2025
@k8s-ci-robot k8s-ci-robot transferred this issue from kubernetes/kubernetes Jan 27, 2025
@shajmakh
Copy link

Thanks for this initiative, I would like to start contributing to the SIG and a Europe-friendly timeslot would definitely help me a lot!

@palnabarun
Copy link
Member

Thanks for choosing to have an additional meeting more suitable to Asia/Europe contributors! 🙏🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
Status: Needs Triage
Development

No branches or pull requests

7 participants