-
Notifications
You must be signed in to change notification settings - Fork 78
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
fixed monthly schedule for Diag WG meetings #90
Comments
Works for me. P.S.: For people like me who can't handle timezones - it's 11am PT outside of DST:
|
In meeting yesterday I accidentally said after the TSC meeting, but here I proposed before 🤷♀️. To clarify, I propose the following for the Diag WG monthly meeting and unless there are objections we'll run with this next month. I'll also add to the Node.js calendar. Thanks! Before last TSC meeting each month at 1900 UTC (click to see your regional time). |
I just noticed that next month it's not the last Thursday of the month, just so people don't get it wrong 😃 So it's the Thursday of every 4th week starting on the 20th of April if my math is correct |
Oh, will the meeting time move with DST btw? In most of Europe DST starts in a few days, but the time is specified in UTC which doesn't follow DST - so technically that means that the meeting will be one our later? Or will we move the time to compensate for DST? |
We ended up going with the last Thursday of the month in April. Perhaps we should stick with that? |
I think this can be closed now given the new set of meetings & bi-weekly cadence. Please reactivate if not the case. |
I think it would help consistency and make participation simpler if we start having a fixed monthly time and date for Diag WG meetings as is done for some other Node.js groups. What do you all think?
An initial proposal: Last Thursday of each month at 1900 UTC (click to see your regional time), which would be one hour before the bi-weekly TSC meeting.
NB: Agenda for meetings is set by the
diag-agenda
label across the Node.js repos./cc @nodejs/diagnostics @nodejs/post-mortem
The text was updated successfully, but these errors were encountered: