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

Node.js Diagnostics WorkGroup Meeting 2020-04-22 #381

Closed
mhdawson opened this issue Apr 20, 2020 · 6 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2020-04-22 #381

mhdawson opened this issue Apr 20, 2020 · 6 comments
Assignees
Labels

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 22-Apr-2020 16:30 (04:30 PM):

Timezone Date/Time
US / Pacific Wed 22-Apr-2020 09:30 (09:30 AM)
US / Mountain Wed 22-Apr-2020 10:30 (10:30 AM)
US / Central Wed 22-Apr-2020 11:30 (11:30 AM)
US / Eastern Wed 22-Apr-2020 12:30 (12:30 PM)
London Wed 22-Apr-2020 17:30 (05:30 PM)
Amsterdam Wed 22-Apr-2020 18:30 (06:30 PM)
Moscow Wed 22-Apr-2020 19:30 (07:30 PM)
Chennai Wed 22-Apr-2020 22:00 (10:00 PM)
Hangzhou Thu 23-Apr-2020 00:30 (12:30 AM)
Tokyo Thu 23-Apr-2020 01:30 (01:30 AM)
Sydney Thu 23-Apr-2020 02:30 (02:30 AM)

Or in your local time:

Links

Agenda

Extracted from diag-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/diagnostics

  • self nomination to diagnostics working group #379
  • COVID-19 and WG sittings #370
  • proposal: elevate diagnostic report to tier1 #369
  • reportVersion semantics are not defined #349
  • Proposal to drive Diagnostics WG initiatives through user journeys #295
  • Node CPU Profiling Roadmap #148
  • [async_hooks] stable API - tracking issue #124

Invited

  • Diagnostics team: @nodejs/diagnostics

Observers/Guests

Notes

The agenda comes from issues labelled with diag-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

@mhdawson mhdawson self-assigned this Apr 20, 2020
@Qard
Copy link
Member

Qard commented Apr 21, 2020

I'd like to discuss nodejs/node#32891. That can be part of the async_hooks stuff at the end. That's the first step in my async_hooks improvement work. :)

@mmarchini
Copy link
Contributor

Seems like we have a packed agenda again. Should we prioritize the deep dives for this week, since we didn't do it last time?

@gireeshpunathil
Copy link
Member

while few items require just few minutes to discuss, the others could potentially take up the whole time. So many be extending the meeting by half an hour and covering deep dive makes sense?

@legendecas
Copy link
Member

while few items require just few minutes to discuss, the others could potentially take up the whole time. So many be extending the meeting by half an hour and covering deep dive makes sense?

Does it make sense to run the meeting every week for 1 hour as same as now to reduce the burden for each meeting?

@Flarna
Copy link
Member

Flarna commented Apr 22, 2020

Most important for me is to have a recording and notes as the timeframe usually doesn't allow me to participate even I'm interested in several topics.

@github-actions
Copy link

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants