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.

Sign up for GitHub

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

Jump to bottom

Node.js Foundation Diagnostics WorkGroup Meeting 2020-02-12 #354

Closed
mhdawson opened this issue Feb 10, 2020 · 5 comments · Fixed by #356
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2020-02-12 #354

mhdawson opened this issue Feb 10, 2020 · 5 comments · Fixed by #356
Assignees
@mhdawson

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 10, 2020 •
edited by mmarchini
Loading

Time

UTC Wed 12-Feb-2020 17:30 (05:30 PM):

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

  • Future of llnode #355
  • 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 Feb 10, 2020
@gireeshpunathil
Copy link
Member

I am not working this week, so wont make to this instance!

@mmarchini
Copy link
Contributor

mmarchini commented Feb 12, 2020 •
edited
Loading

I forgot we changed the meeting time. Might be a few minutes late

@hekike
Copy link
Contributor

hekike commented Feb 12, 2020

Reminder, today we are doing a deep dive on memory leak related tooling and user-journeys:
notes will go here: https://docs.google.com/document/d/16PeoMhREmJxSbrpyom9Uypl2lJuMsqAfB96oocDTPwQ/edit#

@vdeturckheim
Copy link
Member

Will this still be livestreamed?

@hekike
Copy link
Contributor

hekike commented Feb 12, 2020

Yes

mmarchini added a commit to mmarchini/diagnostics that referenced this issue Feb 12, 2020
@mmarchini
doc: add minutes for meeting 2020-02-12
78a925f 
Closes: nodejs#354
@mmarchini mmarchini mentioned this issue Feb 12, 2020
Merged
mmarchini added a commit that referenced this issue Mar 19, 2020
@mmarchini
doc: add minutes for meeting 2020-02-12
314f489 
PR-URL: #356
Fixes: #354
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhdawson mhdawson

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

doc: add minutes for meeting 2020-02-12 mmarchini/diagnostics
5 participants
@hekike @mmarchini @gireeshpunathil @vdeturckheim @mhdawson