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 2021-03-25 #999

Closed
mhdawson opened this issue Mar 22, 2021 · 4 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2021-03-25 #999

mhdawson opened this issue Mar 22, 2021 · 4 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 22, 2021

Time

UTC Thu 25-Mar-2021 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Thu 25-Mar-2021 13:00 (01:00 PM)
US / Mountain Thu 25-Mar-2021 14:00 (02:00 PM)
US / Central Thu 25-Mar-2021 15:00 (03:00 PM)
US / Eastern Thu 25-Mar-2021 16:00 (04:00 PM)
EU / Western Thu 25-Mar-2021 20:00 (08:00 PM)
EU / Central Thu 25-Mar-2021 21:00 (09:00 PM)
EU / Eastern Thu 25-Mar-2021 22:00 (10:00 PM)
Moscow Thu 25-Mar-2021 23:00 (11:00 PM)
Chennai Fri 26-Mar-2021 01:30 (01:30 AM)
Hangzhou Fri 26-Mar-2021 04:00 (04:00 AM)
Tokyo Fri 26-Mar-2021 05:00 (05:00 AM)
Sydney Fri 26-Mar-2021 07:00 (07: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

  • deps: add Yarn 1.22.5 #37277
  • TLS: improve compliance with shutdown standard, remove hacks #36111
  • Rename default branch from "master" to "main" or something similar #33864

nodejs/TSC

  • Update on Mentoring initiative and looking for interested teams #994
  • Charter Undici WG #975
  • any interest in an RFC process? #962
  • Apple Silicon plan #886

nodejs/admin

  • Enable github pages & subdomain for Undici #590

nodejs/security-wg

  • Potential stagnation of open issues on h1 bounty program #654

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.

Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.


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 22, 2021
@Trott
Copy link
Member

Trott commented Mar 23, 2021

Moderation team update:

@nodejs/moderation @nodejs/tsc @nodejs/community-committee

@tniessen
Copy link
Member

As suggested by @Trott in last week's meeting, I took a look at nodejs/node#36111 and it's quite the rabbit hole. All of nodejs/node#36111, nodejs/node#35946, nodejs/node#35904, nodejs/node#36180, libuv/libuv#3034, libuv/libuv#3035, and libuv/libuv#3036 are related to the issue being discussed there. The change itself looks reasonable but I can't say that I understand the full picture yet.

@mmarchini
Copy link
Contributor

No updates from Future of build toolchain initiative

@mhdawson
Copy link
Member Author

PR for minutes: #1003

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