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.

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

meta: fold the Post-mortem WG into Diagnostics WG #586

Merged
merged 1 commit into from
Aug 24, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 4 additions & 15 deletions WORKING_GROUPS.md
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,6 @@ The [Node.js Code of Conduct][] applies to this WG.
* [Docker](#docker)
* [Addon API](#addon-api)
* [Benchmarking](#benchmarking)
* [Post-mortem](#post-mortem)
* [Release](#release)
* [Security](#security)

Expand Down Expand Up @@ -303,6 +302,10 @@ Responsibilities include:
* Exploring opportunities and gaps, discussing feature requests, and addressing
conflicts in Node.js diagnostics.
* Fostering an ecosystem of diagnostics tools for Node.js.
* Defining and adding interfaces/APIs in order to allow dumps to be generated
when needed.
* Defining and adding common structures to the dumps generated in order to
support tools that want to introspect those dumps.

### i18n

Expand Down Expand Up @@ -408,20 +411,6 @@ Responsibilities include:
* Adding regular execution of chosen benchmarks to Node.js builds
* Tracking/publicizing performance between builds/releases

### [Post-mortem](https://github.com/nodejs/post-mortem)

The Post-mortem Diagnostics Working Group is dedicated to the support
and improvement of postmortem debugging for Node.js. It seeks to
elevate the role of postmortem debugging for Node, to assist in the
development of techniques and tools, and to make techniques and tools
known and available to Node.js users.

Responsibilities include:
* Defining and adding interfaces/APIs in order to allow dumps
to be generated when needed.
* Defining and adding common structures to the dumps generated
in order to support tools that want to introspect those dumps.

### [Release](https://github.com/nodejs/release)

The Release Working Group manages the release process for Node.js.
Expand Down