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 2020-01-29 #351

Closed
mhdawson opened this issue Jan 27, 2020 · 2 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2020-01-29 #351

mhdawson opened this issue Jan 27, 2020 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 29-Jan-2020 17:30 (05:30 PM):

Timezone Date/Time
US / Pacific Wed 29-Jan-2020 09:30 (09:30 AM)
US / Mountain Wed 29-Jan-2020 10:30 (10:30 AM)
US / Central Wed 29-Jan-2020 11:30 (11:30 AM)
US / Eastern Wed 29-Jan-2020 12:30 (12:30 PM)
London Wed 29-Jan-2020 17:30 (05:30 PM)
Amsterdam Wed 29-Jan-2020 18:30 (06:30 PM)
Moscow Wed 29-Jan-2020 20:30 (08:30 PM)
Chennai Wed 29-Jan-2020 23:00 (11:00 PM)
Hangzhou Thu 30-Jan-2020 01:30 (01:30 AM)
Tokyo Thu 30-Jan-2020 02:30 (02:30 AM)
Sydney Thu 30-Jan-2020 04:30 (04: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

@mhdawson mhdawson self-assigned this Jan 27, 2020
@hekike
Copy link
Contributor

hekike commented Jan 28, 2020

Hi, originally we planned to make a memory leak user-journey deep drive on this one, but multiple folks who are interested (myself as well) are out this Wednesday so we are planning to move the deep dive to the next one and hold the usual sync this week. The sync meeting will be run by @gireeshpunathil, thank you! Sorry, about the last-minute change.

@gireeshpunathil
Copy link
Member

We will be discussing #349 in this sitting. Inviting relevant stake holders and interested parties

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