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 2020-03-25 #367

Closed
mhdawson opened this issue Mar 23, 2020 · 1 comment
Closed

Node.js Diagnostics WorkGroup Meeting 2020-03-25 #367

mhdawson opened this issue Mar 23, 2020 · 1 comment
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 25-Mar-2020 16:30 (04:30 PM):

Timezone Date/Time
US / Pacific Wed 25-Mar-2020 09:30 (09:30 AM)
US / Mountain Wed 25-Mar-2020 10:30 (10:30 AM)
US / Central Wed 25-Mar-2020 11:30 (11:30 AM)
US / Eastern Wed 25-Mar-2020 12:30 (12:30 PM)
London Wed 25-Mar-2020 16:30 (04:30 PM)
Amsterdam Wed 25-Mar-2020 17:30 (05:30 PM)
Moscow Wed 25-Mar-2020 19:30 (07:30 PM)
Chennai Wed 25-Mar-2020 22:00 (10:00 PM)
Hangzhou Thu 26-Mar-2020 00:30 (12:30 AM)
Tokyo Thu 26-Mar-2020 01:30 (01:30 AM)
Sydney Thu 26-Mar-2020 03:30 (03: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

  • reportVersion semantics are not defined #349
  • Proposal to drive Diagnostics WG initiatives through user journeys #295
  • Diagnostics "Best Practices" Guide? #211
  • [async_hooks] stable API - tracking issue #124

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

@gireeshpunathil
Copy link
Member

closed via #371

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.

2 participants