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-09-13 #1437

Closed
mhdawson opened this issue Sep 11, 2023 · 14 comments · Fixed by #1448
Closed

Node.js Technical Steering Committee (TSC) Meeting 2023-09-13 #1437

mhdawson opened this issue Sep 11, 2023 · 14 comments · Fixed by #1448
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Sep 11, 2023

Time

UTC Wed 13-Sep-2023 15:00 (03:00 PM):

Timezone Date/Time
US / Pacific Wed 13-Sep-2023 08:00 (08:00 AM)
US / Mountain Wed 13-Sep-2023 09:00 (09:00 AM)
US / Central Wed 13-Sep-2023 10:00 (10:00 AM)
US / Eastern Wed 13-Sep-2023 11:00 (11:00 AM)
EU / Western Wed 13-Sep-2023 16:00 (04:00 PM)
EU / Central Wed 13-Sep-2023 17:00 (05:00 PM)
EU / Eastern Wed 13-Sep-2023 18:00 (06:00 PM)
Moscow Wed 13-Sep-2023 18:00 (06:00 PM)
Chennai Wed 13-Sep-2023 20:30 (08:30 PM)
Hangzhou Wed 13-Sep-2023 23:00 (11:00 PM)
Tokyo Thu 14-Sep-2023 00:00 (12:00 AM)
Sydney Thu 14-Sep-2023 01:00 (01:00 AM)

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

  • websocket: proposal for a new core module #49478
  • Discussion: New “ESM by default” mode #49432

nodejs/citgm

  • lookup: declare bankruptcy on flaky modules #959

nodejs/TSC

  • Additions to import.meta #1430

nodejs/undici

  • expose websocket in node bundle #2217

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 Sep 11, 2023
@mhdawson
Copy link
Member Author

@mcollina can you chair the meeting this week. I have a presentation I'm delivering to a large audience I can't move this week at the meeting time.

@mhdawson
Copy link
Member Author

Removing Next release https://github.com/nodejs/uvwasi/issues/228 as I'd put the wrong label on the issue.

@mcollina
Copy link
Member

I would love to but I'm in London at an event, and I'll have booth duty at that specific time. I can kick off YT if needed.

Should we skip?

@GeoffreyBooth
Copy link
Member

GeoffreyBooth commented Sep 11, 2023

Should we skip?

No, we need to unblock nodejs/citgm#959, unless you’d like to remove your block on that.

I’d also like to discuss nodejs/node#49432. I want to make it happen before 21.0.0 and there aren’t many more weeks left before that, so if the TSC has any concerns with what I’m aiming to do then it would be better to hear those sooner than later.

I’m open to moving the time of this week’s meeting as a one-off if there’s another time that might work for everyone.

@anonrig
Copy link
Member

anonrig commented Sep 11, 2023

I'd also like to discuss #1438

@mcollina
Copy link
Member

We should really cover nodejs/node#49625

@GeoffreyBooth
Copy link
Member

GeoffreyBooth commented Sep 12, 2023

Questions for the TSC to answer re nodejs/node#49432:

  • Does anyone have any concerns about the proposal outlined in the top post at Discussion: New “ESM by default” mode node#49432 (comment)? In particular, any concerns that would motivate a block on a PR that implements what’s proposed here.

  • It was suggested that rather than creating a new flag for this, we expand the scope of --input-type: instead of only affecting STDIN, --eval and --print it would enable all forms of input including files to be treated as ESM by default. Leaving aside what flag name we’d use for the experimental phase, once we think the feature is stable would it be considered a breaking/semver-major change to expand the behaviors modified by --input-type? If that’s a change that we shipped, could it be semver-minor that gets backported?

@mhdawson
Copy link
Member Author

If we can move to the 3-4 timeslot I can chair. If we have another volunteer to chair at the current time we can leave as is. Maybe @gireeshpunathil or @Trott ?

I'll check first thing my morning on Wednesday. If there is a volunteer we'll leave as is, otherwise I'll move to the new time.

@mcollina
Copy link
Member

I will make myself available to chair.

@mhdawson
Copy link
Member Author

@mcollina thanks.

@Trott
Copy link
Member

Trott commented Sep 12, 2023

I'm the one who added the CITGM issue to the agenda, but I am very unlikely to be able to make the meeting this week. I'd say that for now, if we're chipping away at the module failures, we don't need to make any imminent decisions on skipping/removing modules. It's only once everything grinds to a halt again that we'll want to assess where we're at and what (if anything) to do.

@Trott
Copy link
Member

Trott commented Sep 12, 2023

I'm the one who added the CITGM issue to the agenda, but I am very unlikely to be able to make the meeting this week. I'd say that for now, if we're chipping away at the module failures, we don't need to make any imminent decisions on skipping/removing modules. It's only once everything grinds to a halt again that we'll want to assess where we're at and what (if anything) to do.

Oh, looks like consensus has been reached there. I'll remove the label from that pull request.

@jasnell
Copy link
Member

jasnell commented Sep 13, 2023

For CITGM, the consensus on the call was to trim the list of modules that CITGM handles to make things easier for now. Then, longer term, spin up a strategic initiative (champion to be determined) to improve CITGM overall.

@mhdawson
Copy link
Member Author

@mcollina were you planning to PR in minutes for this meeting?

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

Successfully merging a pull request may close this issue.

6 participants