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 2022-03-10 #1184

Closed
mhdawson opened this issue Mar 7, 2022 · 6 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2022-03-10 #1184

mhdawson opened this issue Mar 7, 2022 · 6 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 7, 2022

Time

UTC Thu 10-Mar-2022 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Thu 10-Mar-2022 09:00 (09:00 AM)
US / Mountain Thu 10-Mar-2022 10:00 (10:00 AM)
US / Central Thu 10-Mar-2022 11:00 (11:00 AM)
US / Eastern Thu 10-Mar-2022 12:00 (12:00 PM)
EU / Western Thu 10-Mar-2022 17:00 (05:00 PM)
EU / Central Thu 10-Mar-2022 18:00 (06:00 PM)
EU / Eastern Thu 10-Mar-2022 19:00 (07:00 PM)
Moscow Thu 10-Mar-2022 20:00 (08:00 PM)
Chennai Thu 10-Mar-2022 22:30 (10:30 PM)
Hangzhou Fri 11-Mar-2022 01:00 (01:00 AM)
Tokyo Fri 11-Mar-2022 02:00 (02:00 AM)
Sydney Fri 11-Mar-2022 04:00 (04: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

  • Grant triagers the ability to re-run a failed CI #42125
  • Proposal: Adding a built-in test runner #40954
  • Add a resume-ci label to issues? #40817
  • Rename default branch from "master" to "main" #33864

nodejs/email

  • Email cleanup tracking #182

nodejs/TSC

  • nominating aduh95 as a Moderation Team member #1182
  • Publishing specs for Buffer and EventEmitter #1176
  • [meta] settle on a voting solution #1165

nodejs/admin

  • Bot user for nodejs/corepack #660
  • blocklist import/export #659

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 Mar 7, 2022
@richardlau
Copy link
Member

Going to be late to this one as I have a clash this week (regarding our ARM build infrastructure).

@mhdawson
Copy link
Member Author

mhdawson commented Mar 9, 2022

Next-10 Strategic Initiative Update

  • Suitable types - next step PR in changes to doc style/api guides
  • Single binary exe's discussed in mini-summit but no champion to push forward, should probably still land something so we capture what we agreed would be best way forward
  • Modern http
    • undici landed/being tweaked
  • Documentation
  • Planning for next virtual summit on WASM and Security, 7th of April
  • Planning for sessions at OpenJS World (common, review modern http progress, baseline review, ESM and Observability as technical deep dives)

@targos
Copy link
Member

targos commented Mar 10, 2022

I'm probably going to miss this one.

On V8 currency: V8 9.9 and later are blocked on a Windows compiler issue. We haven't found any work around it yet. There is a V8 issue but no comment on it yet.

@Trott
Copy link
Member

Trott commented Mar 10, 2022

@richardlau
Copy link
Member

Going to be late to this one as I have a clash this week (regarding our ARM build infrastructure).

If I don't make it in time for the discussion on the resume-ci label -- I'm supportive of introducing it and would not block triagers from applying it. I would like to point out though that it's going to be much more complicated to implement than the request-ci label. I added some notes in nodejs/node#40817 (comment) for anyone who wants to tackle implementing it.

@mhdawson
Copy link
Member Author

PR for minutes - #1185

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

4 participants