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

Node.js Diagnostics WorkGroup Meeting 2022-01-18 #520

Closed
mhdawson opened this issue Jan 17, 2022 · 7 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2022-01-18 #520

mhdawson opened this issue Jan 17, 2022 · 7 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 18-Jan-2022 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Tue 18-Jan-2022 08:00 (08:00 AM)
US / Mountain Tue 18-Jan-2022 09:00 (09:00 AM)
US / Central Tue 18-Jan-2022 10:00 (10:00 AM)
US / Eastern Tue 18-Jan-2022 11:00 (11:00 AM)
EU / Western Tue 18-Jan-2022 16:00 (04:00 PM)
EU / Central Tue 18-Jan-2022 17:00 (05:00 PM)
EU / Eastern Tue 18-Jan-2022 18:00 (06:00 PM)
Moscow Tue 18-Jan-2022 19:00 (07:00 PM)
Chennai Tue 18-Jan-2022 21:30 (09:30 PM)
Hangzhou Wed 19-Jan-2022 00:00 (12:00 AM)
Tokyo Wed 19-Jan-2022 01:00 (01:00 AM)
Sydney Wed 19-Jan-2022 03:00 (03:00 AM)

Or in your local time:

Links

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/diagnostics

  • Document async_hooks types purposes #511
  • User Journey tracking documentation #502
  • Identify async_hooks use cases beyond AsyncLocalStorage #437

Invited

  • Diagnostics team: @nodejs/diagnostics

Observers/Guests

Notes

The agenda comes from issues labelled with diag-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

@mhdawson mhdawson self-assigned this Jan 17, 2022
@Qard
Copy link
Member

Qard commented Jan 18, 2022

Going to miss this again. Keep getting other work meetings at the same time. Really not the best time slot for me, regardless of which day. 😞

@bmeck
Copy link
Member

bmeck commented Jan 18, 2022

@Qard what would be a good time

@Qard
Copy link
Member

Qard commented Jan 18, 2022

An hour or two later would be better for me. As it is right now, this always at least overlaps with my sprint meetings. I can skip those occasionally, but I also often get other meetings in this time slot. This week my 8am through 10am is full every day. 😬

@RafaelGSS
Copy link
Member

I'm fine moving this meeting 1 or 2 hours later.

@gireeshpunathil
Copy link
Member

we discussed the potential time slots that work for people, and closed the call earlier. I will come up with an issue to formally discuss and derive at a meeting time that works for all. thanks!

@RafaelGSS
Copy link
Member

So today was canceled?

@gireeshpunathil
Copy link
Member

yes

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

No branches or pull requests

5 participants