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-05-27 #1033

Closed
mhdawson opened this issue May 24, 2021 · 5 comments
Closed

Node.js Technical Steering Committee (TSC) Meeting 2021-05-27 #1033

mhdawson opened this issue May 24, 2021 · 5 comments
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Thu 27-May-2021 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Thu 27-May-2021 14:00 (02:00 PM)
US / Mountain Thu 27-May-2021 15:00 (03:00 PM)
US / Central Thu 27-May-2021 16:00 (04:00 PM)
US / Eastern Thu 27-May-2021 17:00 (05:00 PM)
EU / Western Thu 27-May-2021 22:00 (10:00 PM)
EU / Central Thu 27-May-2021 23:00 (11:00 PM)
EU / Eastern Fri 28-May-2021 00:00 (12:00 AM)
Moscow Fri 28-May-2021 00:00 (12:00 AM)
Chennai Fri 28-May-2021 02:30 (02:30 AM)
Hangzhou Fri 28-May-2021 05:00 (05:00 AM)
Tokyo Fri 28-May-2021 06:00 (06:00 AM)
Sydney Fri 28-May-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

  • Future of the Node HTTP Client #38533
  • Tracking Issue: commit queue issues and feedback #34770
  • Rename default branch from "master" to "main" or something similar #33864
  • Migration of core modules to primordials #30697

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

Trott commented May 25, 2021

Moderation Team Report:

Blocked a bot: https://github.com/nodejs/moderation/issues/453

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

@targos
Copy link
Member

targos commented May 25, 2021

V8 Currency:

@Trott
Copy link
Member

Trott commented May 25, 2021

I know it's frustrating that the merge is being delayed by this. I hope someone knowledgable about this stuff gets to looking at the problem and solving it soon, and I will try to make some time myself to take a look today. (I'll start the V8 compile now so I can jump in later.)

I wish I could say without qualification that this is the system working as intended. Before the node-inspect stuff was in core, various node inspect features broke and nobody noticed until users starting reporting them. This is letting us know that node inspect is broken with this V8 update before we merge/ship it.

Unfortunately, that kind of breaks down if the problem is in the test itself, which seems likely here. (On the other hand, at least we're making the tests more robust, assuming we fix this in a reasonable way.)

@mhdawson
Copy link
Member Author

No meeting, was just myself, Rich and Tobias.

@ronag
Copy link
Member

ronag commented May 27, 2021

@mhdawson Sorry, I got delayed.

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