@@ -17,7 +17,6 @@ Core Working Groups are created by the
17
17
* [ Docker] ( #docker )
18
18
* [ Evangelism] ( #evangelism )
19
19
* [ i18n] ( #i18n )
20
- * [ Post-mortem] ( #post-mortem )
21
20
* [ Release] ( #release )
22
21
* [ Security] ( #security )
23
22
* [ Streams] ( #streams )
@@ -89,6 +88,10 @@ Responsibilities include:
89
88
* Exploring opportunities and gaps, discussing feature requests, and addressing
90
89
conflicts in Node.js diagnostics.
91
90
* Fostering an ecosystem of diagnostics tools for Node.js.
91
+ * Defining and adding interfaces/APIs in order to allow dumps to be generated
92
+ when needed.
93
+ * Defining and adding common structures to the dumps generated in order to
94
+ support tools that want to introspect those dumps.
92
95
93
96
### [ Docker] ( https://github.com/nodejs/docker-node )
94
97
@@ -167,21 +170,6 @@ Each language community maintains its own membership.
167
170
* [ nodejs-uk - Ukrainian (Українська)] ( https://github.com/nodejs/nodejs-uk )
168
171
* [ nodejs-vi - Vietnamese (Tiếng Việt)] ( https://github.com/nodejs/nodejs-vi )
169
172
170
-
171
- ### [ Post-mortem] ( https://github.com/nodejs/post-mortem )
172
-
173
- The Post-mortem Diagnostics Working Group is dedicated to the support
174
- and improvement of postmortem debugging for Node.js. It seeks to
175
- elevate the role of postmortem debugging for Node, to assist in the
176
- development of techniques and tools, and to make techniques and tools
177
- known and available to Node.js users.
178
-
179
- Responsibilities include:
180
- * Defining and adding interfaces/APIs in order to allow dumps
181
- to be generated when needed.
182
- * Defining and adding common structures to the dumps generated
183
- in order to support tools that want to introspect those dumps.
184
-
185
173
### [ Release] ( https://github.com/nodejs/LTS )
186
174
The Release Working Group manages the release process for Node.js.
187
175
0 commit comments