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 2024-06-27 #639

Closed
mhdawson opened this issue Jun 24, 2024 · 3 comments · Fixed by #640
Closed

Node.js Diagnostics WorkGroup Meeting 2024-06-27 #639

mhdawson opened this issue Jun 24, 2024 · 3 comments · Fixed by #640
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Thu 27-Jun-2024 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Thu 27-Jun-2024 09:00 (09:00 AM)
US / Mountain Thu 27-Jun-2024 10:00 (10:00 AM)
US / Central Thu 27-Jun-2024 11:00 (11:00 AM)
US / Eastern Thu 27-Jun-2024 12:00 (12:00 PM)
EU / Western Thu 27-Jun-2024 17:00 (05:00 PM)
EU / Central Thu 27-Jun-2024 18:00 (06:00 PM)
EU / Eastern Thu 27-Jun-2024 19:00 (07:00 PM)
Moscow Thu 27-Jun-2024 19:00 (07:00 PM)
Chennai Thu 27-Jun-2024 21:30 (09:30 PM)
Hangzhou Fri 28-Jun-2024 00:00 (12:00 AM)
Tokyo Fri 28-Jun-2024 01:00 (01:00 AM)
Sydney Fri 28-Jun-2024 02:00 (02: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.

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 Jun 24, 2024
@legendecas
Copy link
Member

It seems the script didn't put the agenda items in. Just filled in the items in the google doc.

@legendecas
Copy link
Member

Also, it might be worth to mention nodejs/node#53593.

@RafaelGSS
Copy link
Member

@Qard Will you host today's meeting?

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

Successfully merging a pull request may close this issue.

3 participants