Node.js Technical Steering Committee (TSC) Meeting 2020-08-27

[mhdawson]

Time

UTC Thu 27-Aug-2020 20:00 (08:00 PM):

Timezone	Date/Time
US / Pacific	Thu 27-Aug-2020 13:00 (01:00 PM)
US / Mountain	Thu 27-Aug-2020 14:00 (02:00 PM)
US / Central	Thu 27-Aug-2020 15:00 (03:00 PM)
US / Eastern	Thu 27-Aug-2020 16:00 (04:00 PM)
London	Thu 27-Aug-2020 21:00 (09:00 PM)
Amsterdam	Thu 27-Aug-2020 22:00 (10:00 PM)
Moscow	Thu 27-Aug-2020 23:00 (11:00 PM)
Chennai	Fri 28-Aug-2020 01:30 (01:30 AM)
Hangzhou	Fri 28-Aug-2020 04:00 (04:00 AM)
Tokyo	Fri 28-Aug-2020 05:00 (05:00 AM)
Sydney	Fri 28-Aug-2020 06:00 (06:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2020-08-27&iso=20200827T20
• or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Aug+27%2C+2020+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1KMEFd2RMoRNe3qIAQSZeLs1tDp3Fxxoka4i_EAa2Ql8/edit

Agenda

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

nodejs/node

• [v14.x backport] stream: simpler and faster Readable async iterator #34887
• Rename default branch from "master" to "main" or something similar #33864
• process: Change default --unhandled-rejections=throw #33021

nodejs/nodejs.org

• blm: convert to button #3306

nodejs/TSC

• Package manager manager ... discussion #904

nodejs/admin

• Audit Google account access #389

Invited

• Anatoli Papirovski @apapirovski (TSC)
• Beth Griggs @BethGriggs (TSC)
• Ruben Bridgewater @BridgeAR (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Shelley Vohr @codebytere (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gabriel Schulhof @gabrielschulhof (TSC)
• Gireesh Punathil @gireeshpunathil (TSC)
• James Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Mary Marchini @mmarchini (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Michaël Zasso @targos (TSC)
• Tobias Nießen @tniessen (TSC)
• Rich Trott @Trott (TSC)

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

[Trott]

Moderation Team update: Blocked a user for disruptive content-free PR and notifications. https://github.com/nodejs/moderation/issues/374

No other moderation team actions.

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

[mmarchini]

Remembering we'll be discussing (and potentially voting on) nodejs/node#33021 this week. The survey is closed and the results are available at https://www.surveymonkey.com/results/SM-82X6PX3B7/.

Edit: reading our charter, we need to call for a vote during the meeting, and the call for a vote has to be seconded by a majority of the TSC. So I think we'll only discuss and try to reach consensus, if someone objects we might go to a vote.

[mcollina]

I won't be joining the call so here is my opinion: we should default to throw, i.e. crash by default but allow folks to override if they want to. I second bringing a vote on the matter.

[jasnell]

For #904, we really ought to invite @arcanis to join.

[benjamingr]

I am also in favour of throw or strict as the default for unhandled rejections and I think the survey results reinforce that this is how (at least big parts) of our community feels about it as well.

I think that there is also an education gap we should address (devs don't know our hooks). Looking forward to hear how the meeting goes!

[mmarchini]

It's worth noting that the overwhelming majority of responders work primarily on web servers, so the results might be skewed towards this kind of development environment. I'm still waiting on the raw responses from the Foundation, which might allow us to correlate some responses and get some extra insights.

[benjamingr]

It's worth noting that the overwhelming majority of responders work primarily on web servers

I mean I might be understanding things incorrectly here but doesn't that likely just mean most Node devs (that cared and answered the survey) mostly work on web servers?

While there are lot of non-server use cases I always assumed that is in the most popular way to use Node as a developer by far (where CLIs are probably more popular to consume servers are probably the most popular to develop - but that's just my intuition).

It is also worth mentioning that it's the use-case here in particular (unhandledRejection behavior) is a lot more important in my opinion in web servers since in CLIs there is usually a user that can read the warning in stderr.

I'm still waiting on the raw responses from the Foundation, which might allow us to correlate some responses and get some extra insights.

That would be interesting 👍

[ljharb]

I don't think 2k responses can be extrapolated to "most node devs" even with a qualifier.

[arcanis]

For #904, we really ought to invite @arcanis to join.

That would be fine by me - can I lock the slot in my calendar?

[mhdawson]

@arcanis I'll send you the info you need to join the meeting

[MylesBorins]

@ljharb from an online sample size calculator they are claiming a sample size of 2401 would be good enough to represent a population of 10 million

[ljharb]

@MylesBorins the stats for minimum sample size include a lot of assumptions that i'm not sure have been proven here, including that all node developers are equally represented in the sample. I'm not arguing the reverse (that "most node devs" are not represented here) because i think it's disingenuous to argue either position.

[mmarchini]

Future of Build Toolchain update: repository create to better organize discussions and track progress. Will start creating individual issues for the many topics raised on #901 next.

[mhdawson]

PR minutes: #914