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-08 #374

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

Node.js Diagnostics WorkGroup Meeting 2020-04-08 #374

mhdawson opened this issue Apr 6, 2020 · 12 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Apr 6, 2020

Time

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

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

  • 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
  • Diagnostics "Best Practices" Guide? #211
  • [async_hooks] stable API - tracking issue #124
  • Node CPU Profiling Roadmap #148

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 6, 2020
@mmarchini
Copy link
Contributor

Adding #148 to the agenda (I thought I added the tag during the weekend... I probably don't know how to use the GitHub mobile app yet).

The meeting tomorrow overlaps with TSC meeting, so I might join late. I'll try to join before we get to the async_hooks and CPU Profiling topics since I'm interested in discussing both.

@mmarchini
Copy link
Contributor

Another topic for the meeting: we're adding "Action Items" in our meeting notes, but it's really hard to track those. Any suggestions on how to improve it?

@hekike
Copy link
Contributor

hekike commented Apr 8, 2020

Zoom says "You have an ongoing meeting, you need to end before start a new one..." I'm wondering if it's the TSC meeting and I shouldn't press yes. Any idea?

@gireeshpunathil
Copy link
Member

TSC is ongoing, yes.

@Qard
Copy link
Member

Qard commented Apr 8, 2020

Should we just delay the 30 minutes until it's done then?

@hekike
Copy link
Contributor

hekike commented Apr 8, 2020

So we can only run one meeting at the time?

@mmarchini
Copy link
Contributor

So we can only run one meeting at the time?

On the foundation, yes (maybe we have two accounts, @mhdawson will be able to answer this better).

@hekike
Copy link
Contributor

hekike commented Apr 8, 2020

Alternatives:

  1. Use Netflix Hangouts 🔢 (emoji: 1234)
  2. Delay 30 minutes ⚡️ (emoji: zap)

Please vote

@mmarchini
Copy link
Contributor

@MylesBorins will provide a link to another Zoom account.

@legendecas
Copy link
Member

Alternatives:

  1. Use Netflix Hangouts 🔢 (emoji: 1234)
  2. Delay 30 minutes ⚡️ (emoji: zap)

Please vote

I guess it's not possible to use emojis in reactions that not in the GitHub allow list.

@Qard
Copy link
Member

Qard commented Apr 8, 2020

I'm fine with just waiting until the TSC meeting is over. We've already delayed ten minutes anyway, what's another twenty? 🤷‍♂

@MylesBorins
Copy link

Hey all, got another zoom up

https://zoom.us/j/514087680

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

7 participants