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-05-20 #390

Closed
mhdawson opened this issue May 18, 2020 · 5 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2020-05-20 #390

mhdawson opened this issue May 18, 2020 · 5 comments
Assignees
Labels

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 20-May-2020 16:30 (04:30 PM):

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

  • Discuss usage and support of eBPF #386
  • COVID-19 and WG sittings #370
  • reportVersion semantics are not defined #349
  • 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 May 18, 2020
@gireeshpunathil
Copy link
Member

I would like to propose collab-summit session proposal (openjs-foundation/summit#236) from diag WG as well, to be added to agenda.

@hekike
Copy link
Contributor

hekike commented May 19, 2020

Unfortunately I've less time recently to focus on this working group and would like to hand over the chairmanship to someone who has both the expertise in the field and is passionate about diagnostics. I'd like to discuss tomorrow how can I step down from my duties and what's the election process for a new chairman. I believe this group will greatly benefit from having someone has more time to orchestrate our work in the long term.

I know for example @mmarchini would be happy to take over this role, but maybe multiple folks would be interested, so please think about who would be interested and we should discuss the process and timeline of choosing a new chairman.

@mmarchini
Copy link
Contributor

@gireeshpunathil what do you have in mind? Given the online format, I'm not sure a generic session would be productive or helpful, and a session to continue deep dives would be using a slot from the summit for something we already do regularly. I think it would be useful to have a session similar to the one we had on Vancouver in 2018, where we discussed some specific topics (like Mike's asynchronous continuation proposal). As an example, if we had a session to discuss tracing architecture in core, I think that would be amazing (and it falls under the umbrella of the diagnostics working group).

@gireeshpunathil
Copy link
Member

thanks @mmarchini . few points:

  • we don't have to stick to one proposal
  • tracing arch in core - looks great to me

in short, items that benefit from wider discussions

@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

4 participants