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 Technical Steering Committee (TSC) Meeting 2023-08-16 #1427

Closed
mhdawson opened this issue Aug 14, 2023 · 3 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2023-08-16 #1427

mhdawson opened this issue Aug 14, 2023 · 3 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 16-Aug-2023 13:00 (01:00 PM):

Timezone Date/Time
US / Pacific Wed 16-Aug-2023 06:00 (06:00 AM)
US / Mountain Wed 16-Aug-2023 07:00 (07:00 AM)
US / Central Wed 16-Aug-2023 08:00 (08:00 AM)
US / Eastern Wed 16-Aug-2023 09:00 (09:00 AM)
EU / Western Wed 16-Aug-2023 14:00 (02:00 PM)
EU / Central Wed 16-Aug-2023 15:00 (03:00 PM)
EU / Eastern Wed 16-Aug-2023 16:00 (04:00 PM)
Moscow Wed 16-Aug-2023 16:00 (04:00 PM)
Chennai Wed 16-Aug-2023 18:30 (06:30 PM)
Hangzhou Wed 16-Aug-2023 21:00 (09:00 PM)
Tokyo Wed 16-Aug-2023 22:00 (10:00 PM)
Sydney Wed 16-Aug-2023 23:00 (11:00 PM)

Or in your local time:

Links

Agenda

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

nodejs/node

  • src: add built-in .env file support #48890
  • esm: add import.meta.dirname and import.meta.filename #48740

nodejs/TSC

  • Collaborator Meeting before the NodeConfEU #1422
  • Freeze releases and website changes, pending cache fixes? #1416
  • Remaining OSSF Funding #1384

nodejs/admin

  • Enable GitHub Codespaces for Node.js #808

Invited

Observers/Guests

Notes

The agenda comes from issues labelled with tsc-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

Zoom link: https://zoom.us/j/611357642
Regular password

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.


Invitees

Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet
@mhdawson mhdawson self-assigned this Aug 14, 2023
@anonrig
Copy link
Member

anonrig commented Aug 14, 2023

As a follow-up for the .env pull request I've created an issue: nodejs/node#49148. I recommend going over this in the context of .env pull request that has the tsc-agenda label.

@GeoffreyBooth
Copy link
Member

Re nodejs/node#48740, I opened a proposal in the WinterCG repo: wintercg/proposal-minimum-common-api#54. Unfortunately no one from Bun or Deno has commented on the proposal yet, though it’s only been a few days. I think if we hear nothing by midweek maybe we should start reaching out? I think the goal would be to try to get some version of this proposal landed (or ready to land) before next month’s WinterCG meeting, so that once it’s landed we can update nodejs/node#48740 if necessary and then land it.

In loaders news, we’ve just about reached our milestone for stability: https://github.com/nodejs/loaders#milestone-2-stability. This week’s release should include everything except removing the globalPreload hook, which should be ready to land before the following release (and we wanted to space that out anyway, so that there was at least one release with both globalPreload and its replacement initialize); once the removal PR lands, then the overall API is ready to go into “release candidate” stage and we’ll await bug reports and hopefully make no more API changes. I’d like to get into RC this month and go stable as soon as October with Node 21. That would give us something to announce with the 21.0.0 release.

@mhdawson
Copy link
Member Author

closing as long past.

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