Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-10-24

[mhdawson]

Time

UTC Wed 24-Oct-2018 12:00 (12:00 PM):

Timezone	Date/Time
US / Pacific	Wed 24-Oct-2018 05:00 (05:00 AM)
US / Mountain	Wed 24-Oct-2018 06:00 (06:00 AM)
US / Central	Wed 24-Oct-2018 07:00 (07:00 AM)
US / Eastern	Wed 24-Oct-2018 08:00 (08:00 AM)
London	Wed 24-Oct-2018 13:00 (01:00 PM)
Amsterdam	Wed 24-Oct-2018 14:00 (02:00 PM)
Moscow	Wed 24-Oct-2018 15:00 (03:00 PM)
Chennai	Wed 24-Oct-2018 17:30 (05:30 PM)
Hangzhou	Wed 24-Oct-2018 20:00 (08:00 PM)
Tokyo	Wed 24-Oct-2018 21:00 (09:00 PM)
Sydney	Wed 24-Oct-2018 23:00 (11:00 PM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2018-10-24&iso=20181024T12
• or http://www.wolframalpha.com/input/?i=12PM+UTC%2C+Oct+24%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1v0U7SdJT7_4n2VfttInJgERtvcMib-Ji1AdgezLHum8/edit

Agenda

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

nodejs/node

• buffer: fix crash for invalid index types #23795

nodejs/TSC

• Tracking issue for updating TSC on Board Meetings #476
• Strategic Initiatives - Tracking Issue #423

Invited

• Anna Henningsen @addaleax (TSC)
• Anatoli Papirovski @apapirovski (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Gabriel Schulhof @gabrielschulhof (TSC)
• Gibson Fahnestock @gibfahn (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• James M Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Myles Borins @MylesBorins (TSC)
• Ali Ijaz Sheikh @ofrobots (TSC)
• Rod Vagg @rvagg (TSC)
• Michaël Zasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Timothy Gu @TimothyGu (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]

nodejs/node#23795 is the only non-standing issue on the agenda tomorrow. Seems pretty straightforward and manageable in scope, so hopefully everyone can arrive at the meeting informed and ready to make a decision. (I personally don't think there's much to be gained by kicking it back to GitHub at this point.)

If you will not be at the meeting, it would be hugely helpful if you could comment in the pull request so that we can count your vote in your absence. @addaleax indicates in the PR that she intends to call for a vote.

[addaleax]

I’ve removed my item in the agenda, but I’d still appreciate any look I can get on the PR.

More importantly, I’d like a clear indication that we have always considered hard crashes through the public API a bug so far, and that we don’t intend to change that. I had added the label after @refack’s first review still read “Let 11 crash.” without the addition to the sentence, which seemed like directly conflicting with our previous policies, even if implicit. There is sadly no edit history for reviews, as it seems, so that context went missing.

[joyeecheung]

I’d like a clear indication that we have always considered hard crashes through the public API a bug so far, and that we don’t intend to change that

@addaleax Do you think this is something that can go into the C++ style guide? (although it's not the C++'s side that's solely responsible of these crashes most of the times)

[thefourtheye]

I would like to bring up nodejs/node#23433.

[thefourtheye]

Moderation Team Report:

• Blocked a user for spammy PR (https://github.com/nodejs/moderation/issues/238)

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

[mhdawson]

PR for minutes: #616