Skip to content

Commit 1a82cfc

Browse files
doc: add meeting minutes for 05th April 2022
Fixes: #552 PR-URL: #553 Reviewed-By: Chengzhong Wu <[email protected]> Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Tony Gorez <[email protected]>
1 parent 3b7d31a commit 1a82cfc

File tree

1 file changed

+57
-0
lines changed

1 file changed

+57
-0
lines changed

wg-meetings/2022-04-05.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
# Node.js Diagnostics WorkGroup Meeting 2022-04-05
2+
3+
## Links
4+
5+
* **Recording**: https://www.youtube.com/watch?v=jqMXH85fDRk
6+
* **GitHub Issue**: https://github.com/nodejs/diagnostics/issues/552
7+
* **Minutes Google Doc**: https://docs.google.com/document/d/1Z9embxHZtLbDrNX3WJeJUrA0D-A_n7L4AxrqjdQa6as/edit
8+
9+
## Present
10+
11+
* Diagnostics team: @nodejs/diagnostics
12+
13+
* Gireesh Punathi (@gireeshpunathil)
14+
* Rafael Gonzaga (@rafaelgss)
15+
* Chengzhong Wu (@legendecas)
16+
* Tony Gorez (@tony-go)
17+
18+
19+
## Agenda
20+
21+
## Announcements
22+
WG meeting scheduled in two slots: 3.30 PM UTC and 10.30 PM UTC, with bi-weekly cadence
23+
24+
*Extracted from **diag-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
25+
26+
### nodejs/node
27+
28+
* Contextual and GC friendly perf_hooks user timing [#42503](https://github.com/nodejs/node/issues/42503)
29+
30+
* legendecas: In performance APIs, the user-timing entries are identified by marks and measures, and are prone to name collision. https://github.com/w3c/user-timing/issues/86 is addressing this issue to introduce namespaces for user-timing API. This is for the working group's awareness.
31+
32+
### nodejs/diagnostics
33+
34+
* Re-evaluate `mdb_V8` tool in the tier-list [#549](https://github.com/nodejs/diagnostics/issues/549)
35+
* rafael: we don’t have too much information regarding maintainers and usage in the field. Remove from the tool list (action: Tony)
36+
* Re-evaluate node-heapdump in the tools tier-list [#548](https://github.com/nodejs/diagnostics/issues/548)
37+
* looks like this is the same as ‘heapdump’ module.
38+
* gireesh: we have alternative in core, “v8.getHeapSnapshot()”
39+
* remove from the list (action: Tony)
40+
* Re-evaluate `llnode`in the tools tier-list [#547](https://github.com/nodejs/diagnostics/issues/547)
41+
* provides unique capability in dump debugging. Revalidate tier status with Mary
42+
* Re-evaluate Chrome Dev Tools (CDT) tool in the tier-list [#546](https://github.com/nodejs/diagnostics/issues/546)
43+
* Pretty vague on its placement in the tier list, defer to the next meeting
44+
* Re-evaluate Chakracore - time-travel tool in the tier-list [#545](https://github.com/nodejs/diagnostics/issues/545)
45+
* No evidence of usage in the field, remove from the list (action: Tony)
46+
* Re-evaluate `0x` tool tier-list [#538](https://github.com/nodejs/diagnostics/issues/538)
47+
* follow the checklist and move up in the tier list as applicable (action: Rafael)
48+
* Re-evaluate `node-clinic` tool tier-list [#537](https://github.com/nodejs/diagnostics/issues/537)
49+
* follow the checklist and move up in the tier list as applicable (action: Rafael)
50+
51+
## Q&A, Other
52+
53+
## Upcoming Meetings
54+
55+
* **Node.js Project Calendar**: <https://nodejs.org/calendar>
56+
57+
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.

0 commit comments

Comments
 (0)