Diag WG Meeting - 2018-02-21

[mike-kaufman]

Time

UTC Wed 21-Feb-2018 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Wed 21-Feb-2018 13:00 (01:00 PM)
US / Mountain	Wed 21-Feb-2018 14:00 (02:00 PM)
US / Central	Wed 21-Feb-2018 15:00 (03:00 PM)
US / Eastern	Wed 21-Feb-2018 16:00 (04:00 PM)
London	Wed 21-Feb-2018 21:00 (09:00 PM)
Amsterdam	Wed 21-Feb-2018 22:00 (10:00 PM)
Moscow	Thu 22-Feb-2018 00:00 (12:00 AM)
Chennai	Thu 22-Feb-2018 02:30 (02:30 AM)
Hangzhou	Thu 22-Feb-2018 05:00 (05:00 AM)
Tokyo	Thu 22-Feb-2018 06:00 (06:00 AM)
Sydney	Thu 22-Feb-2018 08:00 (08:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Diagnostics%20Working%20Group+Meeting+2018-02-21&iso=20180221T21
• or http://www.wolframalpha.com/input/?i=09PM+UTC%2C+Feb+21%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1ucTWrJuU7YA-PA2DQraqzIjp3mhf0cyx3tmgGiYw-RA/edit?usp=sharing
• Previous Meeting:
  Minutes: https://github.com/nodejs/diagnostics/blob/master/wg-meetings/2018-02-07.md
  Minutes Google Doc: https://docs.google.com/document/d/1BFmXdY4X2v_LMSSifyvaf6LzMx6nuZx1pbXUJQUTINU/edit?usp=sharing

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

• Integrate C++ AsyncHooks Embedder API with native abstraction #13254

nodejs/diagnostics

• Diag WG meeting times? #158
• Deep dive meeting on CI testing to ensure tools compatibility #156
• Node CPU Profiling Roadmap #148
• Eliminate Monkey Patching for Diagnostic Instrumentation #134
• [async_hooks] stable API - tracking issue #124
• Diagnostics WG Summit - Feb 12-13, 2018 - Ottawa, ON Canada #121
• Async-context formalization and diagnostics support #107
• [trace_event] tracking issue #84

nodejs/benchmarking

• Perf/Node.js #168

Invited

*@nodejs/diagnostics

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

Hangout: https://hangouts.google.com/hangouts/_/ytl/kDSa6Vp_Fu-yg8sMzPdlMYL6jNAjyJpHde4aDM41Ovw=?eid=100598160817214911030&hl=en_US
You Tube: http://youtu.be/RyUR6Ec4BQs

[mike-kaufman]

/cc @nodejs/diagnostics - this is scheduled for 1PM PST wed 2/21. It's on agenda to discuss alternate times for this meeting - see #158.

[AndreasMadsen]

Hehe, can’t make it because of the timing ;)

[mhdawson]

I'm at the Index conf in sf, so I'm not sure if I'll be able to make it.

[mcollina]

I will not be able to join as I'm traveling.

[ofrobots]

I am traveling and won't be able to join.

…

On Wed, Feb 21, 2018, 2:29 PM Matteo Collina ***@***.***> wrote: I will not be able to join as I'm traveling. — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#167 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE0qfwrd7smorCPQwyz6gWoxzqKG8UQks5tW-HvgaJpZM4SMeyk> .

[mike-kaufman]

@mcollina - I assume you closed this by mistake. LMK if not the case.

For folks who can't attend, note we'll be discussing timing of this meeting (issue #158). Plz chime in on 158 if you have any hard conflicts with other issues on the node.js calendar, namely periodic TSC meetings or moderation meetings. See here).

[jkrems]

Got my usual two conflicting day job meetings again today. Earlier time slots would generally work better for me.

[joyeecheung]

It's too late for me so I will not be able to make it.

[mike-kaufman]

Hangout: https://hangouts.google.com/hangouts/_/ytl/kDSa6Vp_Fu-yg8sMzPdlMYL6jNAjyJpHde4aDM41Ovw=?eid=100598160817214911030&hl=en_US
You Tube: http://youtu.be/RyUR6Ec4BQs

/cc @nodejs/diagnostics