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 2022-07-12 #570

Closed
mhdawson opened this issue Jul 11, 2022 · 8 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2022-07-12 #570

mhdawson opened this issue Jul 11, 2022 · 8 comments
Assignees
Labels

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 12-Jul-2022 23:00 (11:00 PM):

Timezone Date/Time
US / Pacific Tue 12-Jul-2022 16:00 (04:00 PM)
US / Mountain Tue 12-Jul-2022 17:00 (05:00 PM)
US / Central Tue 12-Jul-2022 18:00 (06:00 PM)
US / Eastern Tue 12-Jul-2022 19:00 (07:00 PM)
EU / Western Wed 13-Jul-2022 00:00 (12:00 AM)
EU / Central Wed 13-Jul-2022 01:00 (01:00 AM)
EU / Eastern Wed 13-Jul-2022 02:00 (02:00 AM)
Moscow Wed 13-Jul-2022 02:00 (02:00 AM)
Chennai Wed 13-Jul-2022 04:30 (04:30 AM)
Hangzhou Wed 13-Jul-2022 07:00 (07:00 AM)
Tokyo Wed 13-Jul-2022 08:00 (08:00 AM)
Sydney Wed 13-Jul-2022 09:00 (09:00 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

  • Re-evaluate eBPF Tracing tool tier-list #535
  • re-assess the tooling list and their maturity status #532
  • User Journey tracking documentation #502

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 Jul 11, 2022
@gireeshpunathil
Copy link
Member

did this happen?

@RafaelGSS
Copy link
Member

I don't think so. Honestly, I believe that none of the meetings scheduled for this time (23:00 UTC) happened at all.

@tony-go
Copy link
Member

tony-go commented Jul 13, 2022

Maybe we should re asses this meeting slot, maybe it's not the best fit.

@gireeshpunathil
Copy link
Member

@Qard / @mhdawson - does this time slot still work for you? (Mary was the other person who signed up for this slot who is on long holiday I guess)

@mhdawson
Copy link
Member Author

This time slot does not work for me.

@mhdawson
Copy link
Member Author

I can't remember when we adjusted the timeslot. It's possible that the daylight savings time switch is what meant it is just too late for me.

@Qard
Copy link
Member

Qard commented Jul 14, 2022

Oh, sorry, thought I had already mentioned...I'm travelling in Asia until September so that time slot is middle of the night for me now. 😐

@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

No branches or pull requests

5 participants