search

nodejs / diagnostics

Node.js Diagnostics Working Group
MIT License
537 stars 78 forks source link

New meeting day/time? #638

Closed Qard closed 3 months ago

Qard commented 3 months ago

The current time is always in conflict for me (for anyone working on Node.js at Datadog, actually) and I've also heard from others the time is not great. Can we adjust the day/time of the meetings? What days/times are free for other folks?

My Wednesdays through Fridays are mostly free in the time range that is good for EU overlap. Mondays and Tuesdays are full of meetings for me. Do we want to try same time on another day? Or even slightly earlier would be fine too. Much earlier though and we lose accessibility for folks in San Francisco/Seattle/Vancouver.

Also, I am able to host the meetings now, so I can ensure we keep things running more consistently going forward. 😄

cc @nodejs/diagnostics

jsumners-nr commented 3 months ago

Most of my company meetings happen on Tuesdays. But I am almost always open prior to 11:00 EDT. On days other than Tuesday, I have a stand-up at 13:30 EDT every day, but not much else.

tony-go commented 3 months ago

The current time is always in conflict for me

Same for me. This is why I struggle to attend meetings these days.

Wednesday and Thursday work better for me.

RafaelGSS commented 3 months ago

cc: @santigimeno @trevnorris

mhdawson commented 3 months ago

The current time always seems to conflict for me as well.

AbhiPrasad commented 3 months ago

Anytime Wednesday, Thursday, Friday works well with me. Note that the OpenTelemetry JavaScript SIG is at 12 PM EST on Wednesday, so ideally we avoid conflicting with that to encourage contributors between the two organizations to attend meetings.

Qard commented 3 months ago

Does Wednesday at 11AM EST work then? That'd put it one hour before the OTel SIG, so people can block out that time together. Makes sense that many folks would want to attend both meetings.

Any objections to Wed 11AM EST? That's 8AM PST, 5PM CET--on the edge of too early for west coast AMER and may overlap with EMEA dinner time, but I think that's likely the most balanced discomfort we're going to get with a single time slot.

legendecas commented 3 months ago

11AM EST would conflict with Node.js TSC meeting for every two weeks

Qard commented 3 months ago

It looks like the TSC slot alternates every week, so we could offset it so it doesn't overlap?

Qard commented 3 months ago

Actually, that overlaps with next-10...so maybe Thursday would be better? Could do 12PM EST/9AM PST/6PM CET to also not overlap with security or release WGs.

Any objections to Thursday at 12PM EST/9AM PST/6PM CET, or would overlapping with next-10 be a preferable time slot for most people?

jsumners-nr commented 3 months ago

Any objections to Thursday at 12PM EST/

This works best for me.

legendecas commented 3 months ago

Thursday at 12PM EST looks good. I think Node.js zoom would not allow overlapping meetings.

mhdawson commented 3 months ago

Correct that we cannot have two meetings at the same time

Qard commented 3 months ago

Thursday at 12PM EST it is. Who has calendar-adjusting powers? @mhdawson Can you update that and I'll take over running those events again?

tony-go commented 3 months ago

Any objections to Thursday at 12PM EST/

It works for me.

mhdawson commented 3 months ago

@Qard moved in the calendar. Next meeting is on Thursday the 27th at 12 ET.

Qard commented 3 months ago

Thanks! 🙇🏻

legendecas commented 3 months ago

Closing since the new time is set.