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 2023-05-30 #613

Closed
mhdawson opened this issue May 29, 2023 · 4 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2023-05-30 #613

mhdawson opened this issue May 29, 2023 · 4 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 30-May-2023 15:30 (03:30 PM):

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

  • TC39 proposal AsyncContext #608
  • User Journey tracking documentation #502

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 May 29, 2023
@mhdawson
Copy link
Member Author

Unfortunately I'm out Tuesday this week and won't be able to make the meeting. Would be great if #614 was discussed and any agreement/disagreement added to the issue.

@RafaelGSS
Copy link
Member

I have a conflicting meeting as well. However, besides the AsyncContext, I don't think we have something to discuss/share.

Unless we create a new initiative, probably the "news" will be empty as most of the group for now.

@Qard
Copy link
Member

Qard commented May 30, 2023

Sorry, I also had conflicts. 😞

@gireeshpunathil
Copy link
Member

we briefly met, but did not discuss agenda items due to lack of participants.

If any items cannot wait till next month, please let me know, and we can have an ad-hoc meeting at a convenient time for everyone, or else we can make progress through the issue work item itself.

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