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

doc: update Diag WG info #9329

Merged
merged 1 commit into from
Nov 3, 2016
Merged

doc: update Diag WG info #9329

merged 1 commit into from
Nov 3, 2016

Conversation

joshgav
Copy link
Contributor

@joshgav joshgav commented Oct 27, 2016

Checklist
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

doc

Description of change

Updates info on Diagnostics WG (https://github.com/nodejs/diagnostics).

Fixes nodejs/diagnostics#69

/cc @nodejs/diagnostics

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Oct 27, 2016
@mscdex mscdex added the doc Issues and PRs related to the documentations. label Oct 27, 2016
* Fostering a tracing and debugging ecosystem.

* Collaborate with V8 to integrate `v8_inspector`.
* Collaborate with V8 to integrate `trace_event`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

*with VMs

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it's to integrate these with Node itself, such as updating the built-in debugger and updating docs for inspector, or collaborating on #9304.

Will update text accordingly.


* Collaborate with V8 to integrate `v8_inspector`.
* Collaborate with V8 to integrate `trace_event`.
* Maintain and improve `async_wrap` and `async_hooks`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this falls under the core collaborators rather than this specific group?

Copy link
Member

@AndreasMadsen AndreasMadsen Oct 28, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So far implementing async_wrap has been monitored by the Diagnostic WG. We have maintained the unofficial documentation, issue lists and I/Trevor provides monthly status updates. We also have quite a few APM members, who provides us with usecase information though the WG meetings and issues.

I don't know if maintaining is a part of this, but improving definitely does. Once async_hooks lands we may want to revisit that.

@Fishrock123
Copy link
Contributor

I think we should update the wording on some things

* Collaborate with V8 to integrate `trace_event`.
* Maintain and improve `async_wrap` and `async_hooks`.
* Maintain and improve OS trace system integration (e.g. ETW, LTTNG, dtrace).
* Document diagnostic capabilities and APIs in Node and its components.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node.js

* Maintain and improve OS trace system integration (e.g. ETW, LTTNG, dtrace).
* Document diagnostic capabilities and APIs in Node and its components.
* Explore opportunities and gaps, discuss feature requests, and address
conflicts in Node diagnostics.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node.js

* Document diagnostic capabilities and APIs in Node and its components.
* Explore opportunities and gaps, discuss feature requests, and address
conflicts in Node diagnostics.
* Foster an ecosystem of diagnostics tools for Node.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Node.js

@joshgav
Copy link
Contributor Author

joshgav commented Oct 31, 2016

Updated, @Fishrock123 @AndreasMadsen PTAL. Thanks!

@AndreasMadsen
Copy link
Member

LGTM

Updates info on Diagnostics WG (https://github.com/nodejs/diagnostics).

PR-URL: nodejs#9329
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
@joshgav joshgav merged commit 1f08d35 into nodejs:master Nov 3, 2016
@joshgav
Copy link
Contributor Author

joshgav commented Nov 3, 2016

Landed in 1f08d35. Thanks!

@joshgav joshgav deleted the add-diag-wg branch November 3, 2016 01:07
evanlucas pushed a commit that referenced this pull request Nov 3, 2016
Updates info on Diagnostics WG (https://github.com/nodejs/diagnostics).

PR-URL: #9329
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this pull request Nov 22, 2016
Updates info on Diagnostics WG (https://github.com/nodejs/diagnostics).

PR-URL: #9329
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this pull request Nov 22, 2016
Updates info on Diagnostics WG (https://github.com/nodejs/diagnostics).

PR-URL: #9329
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
This was referenced Nov 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants