Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-11-01

[mhdawson]

Time

UTC Wed 01-Nov-2017 12:00 (12:00 PM):

Timezone	Date/Time
US / Pacific	Wed 01-Nov-2017 05:00 (05:00 AM)
US / Mountain	Wed 01-Nov-2017 06:00 (06:00 AM)
US / Central	Wed 01-Nov-2017 07:00 (07:00 AM)
US / Eastern	Wed 01-Nov-2017 08:00 (08:00 AM)
Amsterdam	Wed 01-Nov-2017 13:00 (01:00 PM)
Moscow	Wed 01-Nov-2017 15:00 (03:00 PM)
Chennai	Wed 01-Nov-2017 17:30 (05:30 PM)
Hangzhou	Wed 01-Nov-2017 20:00 (08:00 PM)
Tokyo	Wed 01-Nov-2017 21:00 (09:00 PM)
Sydney	Wed 01-Nov-2017 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+2017-11-01&iso=20171101T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Nov+01%2C+2017+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/13XLNVP892_NiP_q3sibDG-X2dZABNPBfVZH7tFzT9ng/edit

Agenda

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

nodejs/node

• stream: move prefixed files into internal/streams. #11957

nodejs/TSC

• doc: initial version of strategic initiatives #399
• Proposal to form a Governance Working Group #383

nodejs/admin

• meta: fix case of extensions on internal docs and move CoC to admin repo #25

Invited

• Anna Henningsen @addaleax (TSC)
• Ben Noordhuis @bnoordhuis (TSC)
• Сковорода Никита Андреевич @ChALkeR (TSC)
• Colin Ihrig @cjihrig (TSC)
• Evan Lucas @evanlucas (TSC)
• Franziska Hinkelmann @fhinkel (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• Fedor Indutny @indutny (TSC)
• James M Snell @jasnell (TSC)
• Joyee Cheung @joyeecheung (TSC)
• Matteo Collina @mcollina (TSC)
• Michael Dawson @mhdawson (TSC)
• Brian White @mscdex (TSC)
• Myles Borins @MylesBorins (TSC)
• Ali Ijaz Sheikh @ofrobots (TSC)
• Rod Vagg @rvagg (TSC)
• MichaëZasso @targos (TSC)
• Sakthipriyan Vairamani @thefourtheye (TSC)
• Trevor Norris @trevnorris (TSC)
• Rich Trott @Trott (TSC)
• Josh Gavant @joshgav (TSC)

Observers

• Bradley Meck @bmeck (GoDaddy/TC39)
• Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
• Kaitlyn Barnard @kbarnard10 (Node.js Foundation Newsletter Curator)
• Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
• William Kapke @williamkapke (Node.js Community Board representative)

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

[mhdawson]

Depending on discussion on #399. Will likely also add section to agenda to discuss the initiatives.

[mcollina]

Unfortunately I would not be able to partecipate.

[rvagg]

I think we agreed to take "Support both OpenSSL 1.1.0 and 1.0.2" #16130 off the list for now? I have an open TODO to write up some stuff about OpenSSL policy. For now, I think #16130 can be handled like a standard semver-minor.

[Trott]

I think we agreed to take "Support both OpenSSL 1.1.0 and 1.0.2" #16130 off the list for now?

@MylesBorins added it to the agenda. OK to take it off, Myles?

[MylesBorins]

OK to take it off, Myles?

I think the issue itself can be dropped, but I have an idea about how we could re-introduce the standup but for updates on initiatives. opened an issue about that #403

[MylesBorins]

@mhdawson can you please include #399

Turns out you proposed exactly what I suggested in my last comment in it 🤣

[williamkapke]

Unfortunately this time won't work out for my schedule. I will not be able to observe this one.

[mscdex]

I won't be able to make this one either.

[mhdawson]

Still setting up the streaming, will be a few more minutes

[mhdawson]

PR for minutes: #407

[cjihrig]

Oops. I forgot this was this morning and was asleep. Sorry.

[ChALkeR]

Sorry, I wasn't able to participate, was not feeling well.

[joshgav]

Wasn't able to make the time this morning, will review notes. Also a couple notable items to share:

• @mike-kaufman scheduled a Diag WG meeting later today: Diag WG Meeting - 2017-11-01 diagnostics#108
• @eugeneo is working on an extensibility model for Inspector functionality: inspector: implement sub process inspection. node#16627