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 Foundation Diagnostics WorkGroup Meeting 2019-11-06 #335

Closed
mhdawson opened this issue Nov 4, 2019 · 8 comments
Closed

Node.js Foundation Diagnostics WorkGroup Meeting 2019-11-06 #335

mhdawson opened this issue Nov 4, 2019 · 8 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Nov 4, 2019

Time

UTC Wed 06-Nov-2019 18:30 (06:30 PM):

Timezone Date/Time
US / Pacific Wed 06-Nov-2019 10:30 (10:30 AM)
US / Mountain Wed 06-Nov-2019 11:30 (11:30 AM)
US / Central Wed 06-Nov-2019 12:30 (12:30 PM)
US / Eastern Wed 06-Nov-2019 13:30 (01:30 PM)
London Wed 06-Nov-2019 18:30 (06:30 PM)
Amsterdam Wed 06-Nov-2019 19:30 (07:30 PM)
Moscow Wed 06-Nov-2019 21:30 (09:30 PM)
Chennai Thu 07-Nov-2019 00:00 (12:00 AM)
Hangzhou Thu 07-Nov-2019 02:30 (02:30 AM)
Tokyo Thu 07-Nov-2019 03:30 (03:30 AM)
Sydney Thu 07-Nov-2019 05:30 (05: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

  • Proposal to drive Diagnostics WG initiatives through user journeys #295
  • Diagnostics "Best Practices" Guide? #211
  • [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 Nov 4, 2019
@robin-rpr
Copy link

Has this meeting been canceled? (I couldn't find any recordings or meeting minutes) =\

@mhdawson
Copy link
Member Author

mhdawson commented Nov 7, 2019

@robin-rpr there was no meeting as we did not have enough attendees. @gireeshpunathil is going to try to find a better time for the meeting.

@gireeshpunathil
Copy link
Member

@robin-rpr - here is a doodle to select a time preference, if you are interested in joining the meeting
https://doodle.com/poll/6u5e88hxg28g6aun

@mhdawson
Copy link
Member Author

mhdawson commented Nov 8, 2019

@gireeshpunathil yes better I see the times in my timezone now, and hopefully everybody else seems them in their timezones.

@robin-rpr
Copy link

@gireeshpunathil Confirming on my end, timezones are now location based :) However, I would suggest adding a few more experimental slots if possible

@gireeshpunathil
Copy link
Member

@robin-rpr - it is possible to do that; one of the challenge in doing that is: the current slots in the doodle represent the possible slots I suitable for me , stretching either side to the best of my possibilities. Adding more slots can bring back the original problem - the current schedule (11 PM my time) is highly inconvenient to people in Asian timezone including me is ONE of the driver for this change proposal, and adding to the right can skew that again I guess. Do you want experimental slots in the left?

@robin-rpr
Copy link

@gireeshpunathil Gotcha! No worries at all, as this poll focuses on this specific issue I'm super happy to keep it that way :)

@gireeshpunathil
Copy link
Member

meeting happened, closing

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