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 2021-12-15 #517

Closed
mhdawson opened this issue Dec 13, 2021 · 3 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2021-12-15 #517

mhdawson opened this issue Dec 13, 2021 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 15-Dec-2021 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 15-Dec-2021 08:00 (08:00 AM)
US / Mountain Wed 15-Dec-2021 09:00 (09:00 AM)
US / Central Wed 15-Dec-2021 10:00 (10:00 AM)
US / Eastern Wed 15-Dec-2021 11:00 (11:00 AM)
EU / Western Wed 15-Dec-2021 16:00 (04:00 PM)
EU / Central Wed 15-Dec-2021 17:00 (05:00 PM)
EU / Eastern Wed 15-Dec-2021 18:00 (06:00 PM)
Moscow Wed 15-Dec-2021 19:00 (07:00 PM)
Chennai Wed 15-Dec-2021 21:30 (09:30 PM)
Hangzhou Thu 16-Dec-2021 00:00 (12:00 AM)
Tokyo Thu 16-Dec-2021 01:00 (01:00 AM)
Sydney Thu 16-Dec-2021 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

  • 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 Dec 13, 2021
@RafaelGSS
Copy link
Member

@mhdawson It was changed to Tuesday following the agreement in #507. Shall we adjust it in some script?

@gireeshpunathil
Copy link
Member

I was supposed to move it, but could not do. Will work with @mhdawson to fix it.

@gireeshpunathil
Copy link
Member

a new issue will be generated for the new timing. closing out this one

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

3 participants