Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-02-28

[mhdawson]

Time

UTC Wed 28-Feb-2018 22:00 (10:00 PM):

Timezone	Date/Time
US / Pacific	Wed 28-Feb-2018 14:00 (02:00 PM)
US / Mountain	Wed 28-Feb-2018 15:00 (03:00 PM)
US / Central	Wed 28-Feb-2018 16:00 (04:00 PM)
US / Eastern	Wed 28-Feb-2018 17:00 (05:00 PM)
London	Wed 28-Feb-2018 22:00 (10:00 PM)
Amsterdam	Wed 28-Feb-2018 23:00 (11:00 PM)
Moscow	Thu 01-Mar-2018 01:00 (01:00 AM)
Chennai	Thu 01-Mar-2018 03:30 (03:30 AM)
Hangzhou	Thu 01-Mar-2018 06:00 (06:00 AM)
Tokyo	Thu 01-Mar-2018 07:00 (07:00 AM)
Sydney	Thu 01-Mar-2018 09:00 (09:00 AM)

Or in your local time:

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

Links

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

Agenda

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

nodejs/node

• process: doc-only deprecate non-string env value #18990
• src: delete process.env values set to undefined #18158
• buffer: runtime-deprecate Buffer ctor by default#15346

nodejs/TSC

• Node.js OpenSSL Strategy #479
• Tracking issue for updating TSC on Board Meetings #476
• Foundation Update from Mark Hinkle
• Strategic Initiatives - Tracking Issue #423

Invited

• Anna Henningsen @addaleax (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Daniel Bevenius @danbev (TSC)
• Evan Lucas @evanlucas (TSC)
• Franziska Hinkelmann @fhinkel (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)
• Trevor Norris @trevnorris (TSC)
• Rich Trott @Trott (TSC)

Observers

• Timothy Gu @TimothyGu (observer)

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

Uberconference; participants should have the link & numbers, contact me if you don't.

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

[TimothyGu]

Again, I won’t be able to make it to this meeting due to a scheduling conflict.

[mhdawson]

Added update from @mrhinkle to the agenda

[Trott]

Note that nodejs/node#18990 is an alternative to nodejs/node#18158 so they can effectively be treated as a single issue.

nodejs/node#18990 has multiple approvals and no rejections. It's also only been open for 22 hours. I don't think there's anything for the TSC to do there.

nodejs/node#18158 was on the agenda last week but we didn't really discuss it much. That PR is opposed by @TimothyGu, @jasnell, and @BridgeAR. It was put on the agenda by @mcollina so that there could be a vote and the thing either lands or gets closed.

I don't think there's much left to say as the discussion seems to have run its course in that issue. And we're unlikely to get @TimothyGu in here for the conversation unless we wait many weeks or choose to meet at a different time. (The conversation is better to have asynchronously in GitHub anyway, IMO. People who can't make a particular meeting time should not be excluded from an important part of the conversation.)

I'm inclined to start recording TSC votes, if no one else objects to that approach.

[mcollina]

I've removed tsc-agenda from both nodejs/node#18990 and nodejs/node#18158. nodejs/node#18990 is less contentious and it's probably going to land instead.

[Trott]

OK, that leaves #479 as the only non-recurring TSC agenda item this time (other than @mrhinkle telling us about Foundation stuff).

It seems to me that @rvagg put #479 on the agenda mostly for awareness and to expedite it. So far, it has no TSC approvals, although some have reviewed it.

Personal opinion only but my short list of people I'd like to see give it a 👍 so it can land is probably any three of @mhdawson @jasnell @MylesBorins and @ofrobots.

Not sure there's much to discuss at the meeting other than saying "Hey, we need to land this or modify it or reject it sooner rather than later, so please go review it."

[Trott]

Personal opinion only but my short list of people I'd like to see give it a 👍 so it can land is probably any three of @mhdawson @jasnell @MylesBorins and @ofrobots.

Oh, @danbev is probably a good choice too, if they have time to do it.

[Trott]

So far, it has no TSC approvals, although some have reviewed it.

And @mcollina approved it just now! 🎉

[Trott]

Added nodejs/node#15346 to the agenda. Here's my relevant comment from that PR copy/pasted:

I'm adding tsc-agenda to this so we can talk about it at our meeting this week.

The TSC has approved runtime-deprecating Buffer constructor in 10.0.0 😱 but also 🤘 but also 😱...

That's not necessarily an approval of this specific implementation. People still need to review and approve this specifically. But there is no need for this to be held up due to concerns about whether or not we want to implement a runtime deprecation. We do, at least for now. (We can always revert if it lands on master, goes out in a nightly or release candidate, and wreaks havoc.)

[Trott]

(In case I'm not at the meeting: We need to talk about how to land it as soon as we can and get the word out as effectively as we can. Also, if there's things we need to do to help prepare the ecosystem, let's talk about what those things are.)

[mhdawson]

Link for the meeting, will send password separately: https://zoom.us/j/349243116

[mhdawson]

Updated invite list, was out of office last week and have not yet updated template. Should be able to do that before next week.

[mrhinkle]

Prosed Agenda for my part (about 10 minutes)

How can I help you?

• Travel funding
• Other resources like training conflict resolution training, Mediation team and beyond
• What community facilitation would you like to see from Node.js Foundation as we staff these resources.
• IRC cloud group license
• Update on the board subcommittee

How our legal committee works

• Foundation Legal Counsel - Andy Updegrove
• Board Legal Committee

Q&A

[danbev]

I'm going to have to skip tonights meeting....got a bad cold and need to sleep.

[fhinkel]

Same here 🤧 🤧