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 2024-04-30 #632

Closed
mhdawson opened this issue Apr 29, 2024 · 3 comments
Closed

Node.js Diagnostics WorkGroup Meeting 2024-04-30 #632

mhdawson opened this issue Apr 29, 2024 · 3 comments
Assignees
Labels

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 30-Apr-2024 15:30 (03:30 PM):

Timezone Date/Time
US / Pacific Tue 30-Apr-2024 08:30 (08:30 AM)
US / Mountain Tue 30-Apr-2024 09:30 (09:30 AM)
US / Central Tue 30-Apr-2024 10:30 (10:30 AM)
US / Eastern Tue 30-Apr-2024 11:30 (11:30 AM)
EU / Western Tue 30-Apr-2024 16:30 (04:30 PM)
EU / Central Tue 30-Apr-2024 17:30 (05:30 PM)
EU / Eastern Tue 30-Apr-2024 18:30 (06:30 PM)
Moscow Tue 30-Apr-2024 18:30 (06:30 PM)
Chennai Tue 30-Apr-2024 21:00 (09:00 PM)
Hangzhou Tue 30-Apr-2024 23:30 (11:30 PM)
Tokyo Wed 01-May-2024 00:30 (12:30 AM)
Sydney Wed 01-May-2024 01:30 (01: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

  • New website is live and the diagnostics section could use some love. ❤️ #630

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 29, 2024
@Qard
Copy link
Member

Qard commented Apr 30, 2024

I would like to add #634 to the topics to discuss today.

@Qard
Copy link
Member

Qard commented Apr 30, 2024

Seems no one showed up today. I would appreciate if members could please look at #634 and comment async if you approve of the transfer of import-in-the-middle to our ownership or if you have any concerns.

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.

@github-actions github-actions bot added the stale label Jul 30, 2024
@Qard Qard closed this as completed Jul 30, 2024
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

2 participants