README
Diagnostics Working Group
The goal of this WG is to ensure Node provides a set of comprehensive, documented, extensible diagnostic protocols, formats, and APIs to enable tool vendors to provide reliable diagnostic tools for Node.
Work needed includes:
- Collect, understand, and document existing diagnostic capabilities and entry-points throughout Node, V8, and other components.
- Collect and document projects and products providing diagnostics for Node with brief description of their technical architecture and sponsoring organizations.
- Identify opportunities and gaps, then propose and implement solutions.
Current Initiatives
| Initiative | Champion | Stakeholders | Links |
|---|---|---|---|
| Diagnostic Channel | @qard | https://github.com/nodejs/diagnostics/issues/180 | |
| Async Hooks | @qard | https://github.com/nodejs/diagnostics/issues/124 | |
| Async Context | @mike-kaufman | @kjin | https://github.com/nodejs/diagnostics/issues/107 |
| Support tiers | @mhdawson | https://github.com/nodejs/diagnostics/issues/157 | |
| CPU Profiling | @mmarchini | https://github.com/nodejs/diagnostics/issues/148 | |
| Post-mortem WG merge | @mmarchini | https://github.com/nodejs/post-mortem/issues/48 | |
| Trace Events | @jasnell | @ofrobots | https://github.com/nodejs/diagnostics/issues/84 |
| CLS | @watson | https://github.com/nodejs/node/pull/26540 |
Need volunteers for
| Initiative | Champion | Links |
|---|---|---|
| Performance Profiles | https://github.com/nodejs/diagnostics/issues/161 | |
| Time-travel debugging | https://github.com/nodejs/diagnostics/issues/164 | |
| Platform neutrality |
Logistics
Semi-monthly Meetings
Meetings of the working group typically occur every other Tuesday, at two different time slots, alternating (3.30 PM UTC and 10.30 PM UTC). A few days before each meeting, an issue will be created with the date and time of the meeting. The issue will provide schedule logistics as well as an agenda, links to meeting minutes, and information about how to join as a participant or a viewer.
Biannual F2F
Twice a year the diagnostics working group meets for a Face to Face gathering where current concerns are hashed out in greater detail. An issue will be created for the event where those who are interested may find details about how to participate.
See the foundation calendar for meeting times.
Members
- @BridgeAR - Ruben Bridgewater
- @cjihrig - Colin Ihrig
- @Flarna - Gerhard Stöbich
- @gireeshpunathil - Gireesh Punathil
- @tony-go - Tony Gorez
- @harshithakp - Harshitha K P
- @hashseed - Yang Guo
- @hekike - Peter Marton
- @jasnell - James M Snell
- @jkrems - Jan Olaf Krems
- @joyeecheung - Joyee Cheung
- @kjin - Kelvin Jin
- @legendecas - Chengzhong Wu
- @mike-kaufman - Mike Kaufman
- @naugtur - Zbyszek Tenerowicz
- @No9 - Anton Whalley
- @ofrobots - Ali Ijaz Sheikh
- @othiym23 - Forrest L Norvell
- @Qard - Stephen Belanger
- @rafaelgss - Rafael Gonzaga
- @sam-github - Sam Roberts
- @watson - Thomas Watson
- @yunong - Yunong Xiao
- @AbhiPrasad - Abhijeet Prasad
- @timfish - Tim Fish
Emeritus
- @AndreasMadsen - Andreas Madsen
- @bnoordhuis - Ben Noordhuis
- @brycebaril - Bryce Baril
- @dberesford - Damian Beresford
- @Fishrock123 - Jeremiah Senkpiel
- @piscisaureus - Bert Belder
- @pmuellr - Patrick Mueller
- @rmg - Ryan Graham
- @GlenTiki - Glen Keane
- @thlorenz - Thorsten Lorenz
- @trevnorris - Trevor Norris
- @danielkhan - Daniel Khan
- @mcollina - Matteo Collina
- @mhdawson - Michael Dawson
- @mmarchini - Mary Marchini
- @Hollerberg - Gernot Reisinger
Contributors
(top 30 of 48)
Similar repos
README
Diagnostics Working Group
The goal of this WG is to ensure Node provides a set of comprehensive, documented, extensible diagnostic protocols, formats, and APIs to enable tool vendors to provide reliable diagnostic tools for Node.
Work needed includes:
- Collect, understand, and document existing diagnostic capabilities and entry-points throughout Node, V8, and other components.
- Collect and document projects and products providing diagnostics for Node with brief description of their technical architecture and sponsoring organizations.
- Identify opportunities and gaps, then propose and implement solutions.
Current Initiatives
| Initiative | Champion | Stakeholders | Links |
|---|---|---|---|
| Diagnostic Channel | @qard | https://github.com/nodejs/diagnostics/issues/180 | |
| Async Hooks | @qard | https://github.com/nodejs/diagnostics/issues/124 | |
| Async Context | @mike-kaufman | @kjin | https://github.com/nodejs/diagnostics/issues/107 |
| Support tiers | @mhdawson | https://github.com/nodejs/diagnostics/issues/157 | |
| CPU Profiling | @mmarchini | https://github.com/nodejs/diagnostics/issues/148 | |
| Post-mortem WG merge | @mmarchini | https://github.com/nodejs/post-mortem/issues/48 | |
| Trace Events | @jasnell | @ofrobots | https://github.com/nodejs/diagnostics/issues/84 |
| CLS | @watson | https://github.com/nodejs/node/pull/26540 |
Need volunteers for
| Initiative | Champion | Links |
|---|---|---|
| Performance Profiles | https://github.com/nodejs/diagnostics/issues/161 | |
| Time-travel debugging | https://github.com/nodejs/diagnostics/issues/164 | |
| Platform neutrality |
Logistics
Semi-monthly Meetings
Meetings of the working group typically occur every other Tuesday, at two different time slots, alternating (3.30 PM UTC and 10.30 PM UTC). A few days before each meeting, an issue will be created with the date and time of the meeting. The issue will provide schedule logistics as well as an agenda, links to meeting minutes, and information about how to join as a participant or a viewer.
Biannual F2F
Twice a year the diagnostics working group meets for a Face to Face gathering where current concerns are hashed out in greater detail. An issue will be created for the event where those who are interested may find details about how to participate.
See the foundation calendar for meeting times.
Members
- @BridgeAR - Ruben Bridgewater
- @cjihrig - Colin Ihrig
- @Flarna - Gerhard Stöbich
- @gireeshpunathil - Gireesh Punathil
- @tony-go - Tony Gorez
- @harshithakp - Harshitha K P
- @hashseed - Yang Guo
- @hekike - Peter Marton
- @jasnell - James M Snell
- @jkrems - Jan Olaf Krems
- @joyeecheung - Joyee Cheung
- @kjin - Kelvin Jin
- @legendecas - Chengzhong Wu
- @mike-kaufman - Mike Kaufman
- @naugtur - Zbyszek Tenerowicz
- @No9 - Anton Whalley
- @ofrobots - Ali Ijaz Sheikh
- @othiym23 - Forrest L Norvell
- @Qard - Stephen Belanger
- @rafaelgss - Rafael Gonzaga
- @sam-github - Sam Roberts
- @watson - Thomas Watson
- @yunong - Yunong Xiao
- @AbhiPrasad - Abhijeet Prasad
- @timfish - Tim Fish
Emeritus
- @AndreasMadsen - Andreas Madsen
- @bnoordhuis - Ben Noordhuis
- @brycebaril - Bryce Baril
- @dberesford - Damian Beresford
- @Fishrock123 - Jeremiah Senkpiel
- @piscisaureus - Bert Belder
- @pmuellr - Patrick Mueller
- @rmg - Ryan Graham
- @GlenTiki - Glen Keane
- @thlorenz - Thorsten Lorenz
- @trevnorris - Trevor Norris
- @danielkhan - Daniel Khan
- @mcollina - Matteo Collina
- @mhdawson - Michael Dawson
- @mmarchini - Mary Marchini
- @Hollerberg - Gernot Reisinger
Similar repos
Contributors
(top 30 of 48)