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

HTML Standard triage meeting times #8106

Closed
domenic opened this issue Jul 14, 2022 · 6 comments
Closed

HTML Standard triage meeting times #8106

domenic opened this issue Jul 14, 2022 · 6 comments

Comments

@domenic
Copy link
Member

domenic commented Jul 14, 2022

The HTML triage meeting (see e.g. #7981) is currently taking place at 18:00 Berlin / 01:00 Tokyo / 09:00 San Francisco every month.

Since I have just moved to Tokyo, this time is no longer as good for me. At the last meeting we discussed a variety of ways to shift this around, so that as one of the editors I could try to attend more often. This also seems like a good thing in general; we already had a couple of APAC attendees (at least @sideshowbarker @saschanaz) who were being subjected to our US/Europe-centered meeting times.

We'll use as our reference the timezones for Tokyo (me, reasonably representative of APAC), Berlin (@annevk, reasonably representative of Europe), and San Francisco (@past, reasonably representative of the US).

Some candidate times are:

There are also other times (e.g. 16:00 Berlin / 23:00 Tokyo / 07:00 San Francisco) which are good for one location and painful-but-doable for two locations. But I think I'd rather avoid that; a recurring meeting that consistently causes people to do work far outside of work hours is not great.

@emilio also mentioned that it'd be bad to consistently wait two months to discuss an agenda item, so if we start rotating times we should consider a more frequent cadence. This seems reasonable to me.

So my proposal is that we switch to a two-week cadence using the above candidate times. The end result is that if you avoid meetings between 00:00-08:00, you can attend 2/3 of all meetings, and you will have a maximum delay of 4 weeks before being able to discuss an agenda item, like is the case today.

Does this sound like a reasonable starting point? Possible tweaks include reducing the frequency to every 3 weeks to reduce total meetings, or changing the times around by an hour or so. Feel free to weigh in on those or suggest more.

@domenic domenic added the agenda+ To be discussed at a triage meeting label Jul 14, 2022
@emilio
Copy link
Contributor

emilio commented Jul 14, 2022

we already had a couple of APAC attendees (at least @sideshowbarker @saschanaz) who were being subjected to our US/Europe-centered meeting times.

FWIW I think @saschanaz is in Europe, but it doesn't change the point :)

So my proposal is that we switch to a two-week cadence using the above candidate times.

That seems pretty reasonable to me. If it ends up being too many meetings we can reduce frequency, but this seems like a good starting point, and seems pretty fair.

@smaug----
Copy link
Collaborator

02:00 Berlin / 09:00 Tokyo / 17:00 San Francisco: APAC + US friendly

That is 03:00 here. Would it be possible to have it one hour earlier? It would be still quite reasonable to Tokyo and SF

@domenic
Copy link
Member Author

domenic commented Jul 21, 2022

If 2am vs. 3am would make a real difference in attendance, then sure, I can wake up an extra hour earlier. I'll update the OP.

@past
Copy link

past commented Jul 21, 2022

This seems like a fine plan to me.

@past
Copy link

past commented Jul 31, 2022

I haven't heard of any concerns, so I'm planning to switch to this new plan after the next meeting, since we had already filed that issue with the current time. If folks prefer we switch this coming week, let me know.

@past
Copy link

past commented Aug 4, 2022

@chrishtr raised the question in the meeting today of whether we should limit the triage meeting to half an hour, since it will now be more frequent. That sounds like a good idea to me, but I wonder what others think. 👍 / 👎 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants