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-02-22 #528

Closed
mhdawson opened this issue Feb 21, 2022 · 5 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2022-02-22 #528

mhdawson opened this issue Feb 21, 2022 · 5 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 22-Feb-2022 16:00 (04:00 PM):

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

  • Move Slack channel to OpenJS Foundation server #527
  • meeting time, again #507
  • 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 Feb 21, 2022
@mhdawson
Copy link
Member Author

I'm not going to be able to make it this time.

@tony-go
Copy link
Member

tony-go commented Feb 21, 2022

I'll be in the plane at this time. I'll watch it on YouTube later

@RafaelGSS
Copy link
Member

As we have discussed in the last meeting, we should define today if we should make it tomorrow or postpone.

I propose for those who can participate, add 👍 in the issue. If less than 3 people react with this flag we can consider it as postponed.

cc: @nodejs/diagnostics

@gireeshpunathil
Copy link
Member

only 2 👍 so far, let us call it postponed then!

@gireeshpunathil
Copy link
Member

moved to next week, 01/03.

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

4 participants