Skip to content

Commit 1b75d4b

Browse files
mhdawsonrvagg
authored andcommitted
doc: update WORKING_GROUPS.md - add missing groups
Add Benchmarking and Post-Mortem workgroups as they were missing. Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #3450
1 parent bf7c3da commit 1b75d4b

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

WORKING_GROUPS.md

+34
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,8 @@ back in to the TSC.
2727
* [Roadmap](#roadmap)
2828
* [Docker](#docker)
2929
* [Addon API](#addon-api)
30+
* [Benchmarking](#benchmarking)
31+
* [Post-mortem](#post-mortem)
3032
* [Starting a Working Group](#starting-a-wg)
3133
* [Bootstrap Governance](#bootstrap-governance)
3234
* [Intl](#Intl)
@@ -219,6 +221,38 @@ Their responsibilities are:
219221
The current members can be found in their
220222
[README](https://github.com/nodejs/nan#collaborators).
221223

224+
### [Benchmarking](https://github.com/nodejs/benchmarking)
225+
226+
The purpose of the Benchmark working group is to gain consensus
227+
for an agreed set of benchmarks that can be used to:
228+
229+
+ track and evangelize performance gains made between Node releases
230+
+ avoid performance regressions between releases
231+
232+
Its responsibilities are:
233+
234+
+ Identify 1 or more benchmarks that reflect customer usage.
235+
Likely need more than one to cover typical Node use cases
236+
including low-latency and high concurrency
237+
+ Work to get community consensus on the list chosen
238+
+ Add regular execution of chosen benchmarks to Node builds
239+
+ Track/publicize performance between builds/releases
240+
241+
### [Post-mortem](https://github.com/nodejs/post-mortem)
242+
243+
The Post-mortem Diagnostics working group is dedicated to the support
244+
and improvement of postmortem debugging for Node.js. It seeks to
245+
elevate the role of postmortem debugging for Node, to assist in the
246+
development of techniques and tools, and to make techniques and tools
247+
known and available to Node.js users.
248+
249+
Its responsibilities are:
250+
251+
+ Defining and adding interfaces/APIs in order to allow dumps
252+
to be generated when needed
253+
+ Defining and adding common structures to the dumps generated
254+
in order to support tools that want to introspect those dumps
255+
222256
## Starting a WG
223257

224258
A Working Group is established by first defining a charter that can be

0 commit comments

Comments
 (0)