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 Foundation Diagnostics WorkGroup Meeting 2018-05-16 #192

Closed
mhdawson opened this issue May 14, 2018 · 3 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2018-05-16 #192

mhdawson opened this issue May 14, 2018 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 16-May-2018 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Wed 16-May-2018 11:00 (11:00 AM)
US / Mountain Wed 16-May-2018 12:00 (12:00 PM)
US / Central Wed 16-May-2018 13:00 (01:00 PM)
US / Eastern Wed 16-May-2018 14:00 (02:00 PM)
London Wed 16-May-2018 19:00 (07:00 PM)
Amsterdam Wed 16-May-2018 20:00 (08:00 PM)
Moscow Wed 16-May-2018 21:00 (09:00 PM)
Chennai Wed 16-May-2018 23:30 (11:30 PM)
Hangzhou Thu 17-May-2018 02:00 (02:00 AM)
Tokyo Thu 17-May-2018 03:00 (03:00 AM)
Sydney Thu 17-May-2018 04:00 (04: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

  • Strategic Initiatives/Champions like we have on TSC #185
  • Diagnostics Channel - Next steps #180
  • Diag WG Deep Dives - topics #168
  • Node CPU Profiling Roadmap #148
  • [async_hooks] stable API - tracking issue #124
  • Async-context formalization and diagnostics support #107
  • [trace_event] tracking issue #84

nodejs/TSC

  • Discuss blocking on Zones proposal #340

Invited

  • Diagnostics team: @nodejs/diagnostics

Observers

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 14, 2018
@mcollina
Copy link
Member

Unforuntately I will not be able to join.

@mmarchini
Copy link
Contributor

Closed by: #195

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