[SIG Scheduling] Negotiating the community meeting time

[kerthcet]

Describe the issue

Refer to https://github.com/kubernetes/community/pull/7215/files#r1153628357

Some context:

We have quite a bit of contributors from APAC, but the scheduled biweekly meeting time is usually too late, so we reached an agreement of another APAC meeting monthly. We have attenders in APAC meeting, but usually very little, and gradually we host the meeting less and less. It acts like the broken windows effect, however, we can not just ignore the meeting in case we do have members attend.

@alculquicondor provides a suggestion here:

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.

So in this thread, we'll discuss about:

• Whether we should cancel the APAC meeting
• Whether we agree to turn the primary meeting to alternated times, also the exact meeting time.
• Or we have other advices

/sig scheduling
cc @kubernetes/sig-scheduling-misc

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kerthcet]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Huang-Wei]

@kerthcet given the current situation of APAC attendance, I may propose to cancel it first until we find a promising slot. WDYT?

[kerthcet]

Agree, seems also no willing to change the current meeting time.

[sanposhiho]

+1 to cancel. Unfortunately, also I personally won't be able to join constantly, even if we change the time.
Can we somehow make the earth flat so that all countries are in the same timezone and everyone can easily join US meeting? No no, never mind.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten