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 Loaders Team Meeting 2023-08-29 #158

Closed
mhdawson opened this issue Aug 25, 2023 · 2 comments
Closed

Node.js Loaders Team Meeting 2023-08-29 #158

mhdawson opened this issue Aug 25, 2023 · 2 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Tue 29-Aug-2023 18:00 (06:00 PM):

Timezone Date/Time
US / Pacific Tue 29-Aug-2023 11:00 (11:00 AM)
US / Mountain Tue 29-Aug-2023 12:00 (12:00 PM)
US / Central Tue 29-Aug-2023 13:00 (01:00 PM)
US / Eastern Tue 29-Aug-2023 14:00 (02:00 PM)
EU / Western Tue 29-Aug-2023 19:00 (07:00 PM)
EU / Central Tue 29-Aug-2023 20:00 (08:00 PM)
EU / Eastern Tue 29-Aug-2023 21:00 (09:00 PM)
Moscow Tue 29-Aug-2023 21:00 (09:00 PM)
Chennai Tue 29-Aug-2023 23:30 (11:30 PM)
Hangzhou Wed 30-Aug-2023 02:00 (02:00 AM)
Tokyo Wed 30-Aug-2023 03:00 (03:00 AM)
Sydney Wed 30-Aug-2023 04:00 (04:00 AM)

Or in your local time:

Links

Agenda

Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

Invited

  • Loaders team: @nodejs/loaders

Observers/Guests

Notes

The agenda comes from issues labelled with loaders-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 Aug 25, 2023
@GeoffreyBooth
Copy link
Member

So nodejs/node#49144 is the last PR to finish Milestone 2, after which we will have finished everything that we need to finish to potentially go stable. Should we perhaps use this meeting time to screenshare and try to resolve any issues with that PR? @JakobJingleheimer @izaakschroeder?

@JakobJingleheimer
Copy link
Member

That would be helpful! I think @aduh95 wrote the bit of code that seems relevant to the issue I'm experiencing.

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