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 Deep Dive Meeting 2020-08-12 #425

Closed
mhdawson opened this issue Aug 10, 2020 · 1 comment
Closed

Node.js Diagnostics Deep Dive Meeting 2020-08-12 #425

mhdawson opened this issue Aug 10, 2020 · 1 comment
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 12-Aug-2020 16:30 (04:30 PM):

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

Or in your local time:

Links

Agenda

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

nodejs/diagnostics

  • Deep Dive Suggestion: triaging existing long-standing issues #416
  • Deep Dive Suggestion: list subsystems which would benefit from trace points #415
  • Continue unified hooks discussion #401
  • Production readiness guide #399
  • Discuss usage and support of eBPF #386
  • Diagnostics Best Practices Guide content definition meeting #254
  • Diagnostics Channel - Next steps #180

Invited

  • Diagnostics deep dive meetings: @nodejs/diagnostics

Observers/Guests

Notes

The agenda comes from issues labelled with diag-deepdive-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 Aug 10, 2020
@mmarchini
Copy link
Contributor

These are the options we have to deep dive tomorrow:

Should we continue/finish the Unexpected Behavior User Journey tomorrow, or do folks want to jump on another topic? I don't think there's much left to discuss on the Unexpected Behavior User Journey.

@Qard Qard closed this as completed Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants