Node.js Foundation Technical Steering Committee (TSC) Meeting 2016-12-15

[rvagg]

Time

UTC Thu 15-Dec-2016 20:00:

Timezone	Date/Time
US / Pacific	Thu 15-Dec-2016 12:00
US / Mountain	Thu 15-Dec-2016 13:00
US / Central	Thu 15-Dec-2016 14:00
US / Eastern	Thu 15-Dec-2016 15:00
Amsterdam	Thu 15-Dec-2016 21:00
Moscow	Thu 15-Dec-2016 23:00
Chennai	Fri 16-Dec-2016 01:30
Tokyo	Fri 16-Dec-2016 05:00
Sydney	Fri 16-Dec-2016 07:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2016-12-15&iso=20161215T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Dec+15%2C+2016+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1gQHht4zN23pbwrDkNjnKv0Bn40nNJ-9Td6AeOHaAHbU
• Previous Minutes Google Doc: https://docs.google.com/document/d/1eUe2T9B7YMKmmAt0iskCP76kmKvhCkdxMdfqTg99yDU

Agenda

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

nodejs/TSC

• Travel fund request for Anna Henningsen for TC39 in January #176
• Formation of a Security Working Group #175
• Updating the Copyright #174
• Utilize travel fund for all CTC / TSC members who want to come to Node Interactive #147
• Add scope of responsibility for TSC ("Define Node Core" cont.) #144
• charter: revised membership rules #142
• Investigate moving nvm into the foundation #96

Invited

• Ben Noordhuis @bnoordhuis (TSC)
• Bryan Hughes @nebrius (TSC)
• Chris Dickinson @chrisdickinson (TSC)
• Colin Ihrig @cjihrig (TSC)
• Jeremiah Senkpiel @Fishrock123 (TSC)
• Fedor Indutny @indutny (TSC)
• James M Snell @jasnell (TSC)
• Josh Gavant @joshgav (observer/Microsoft)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Brian White @mscdex (TSC)
• Bert Belder @piscisaureus (TSC)
• Rod Vagg @rvagg (TSC)
• Shigeki Ohtsu @shigeki (TSC)
• Trevor Norris @trevnorris (TSC)
• William Kapke @williamkapke (observer)
• Jenn Turner @renrutnnej (observer)
• Tracy Hinds @hackygolucky (observer/Node.js Foundation)
• Anna Henningson (observer/CTC)
• Michael Dawson (observer/CTC)

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.

A standing invitation exists for all @nodejs/CTC members who are not also TSC members to attend in observer capacity.

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 it.

[rvagg]

Apologies for not having finished off #144 (define scope) even though I have everything I need to close it out. I believe we can resolve it on GitHub as we have both feedback and a nod from the Board on our plan there.

Re #147 (travel funds for NINA), it's on the agenda because we need to ensure we follow up with everyone who requested funds and make sure they are taken care of. I've only done this with one individual who followed up personally with me, I'm not sure what the status of the rest is but I don't want to be responsible for us dropping the ball!

[rvagg]

Is there someone that can give us an update on version management so we can feel like we're making progress on #96?

[bnoordhuis]

Much as I regret it, I don't think I'll be able to make it; in a bit of a babysitter bind, I'm afraid. Can someone take (private if necessary) notes on #174?

I'm still mystified by @mikeal's reasoning because it's 180 degrees at odds with the advice I got from a copyright lawyer a few years ago, and seems to fly in the face of practices in other open source projects.

[joshgav]

On my backlog is to open an issue on bringing node-inspect into the Foundation, per nodejs/diagnostics#67 and nodejs/node#10187. I hope to get the issue opened shortly, but this is an early FYI in case anyone has feedback now.

@rvagg I can report on the meeting at the Collab Summit on #96 but haven't caught up since then. cc @coreybutler @ljharb

[bnoordhuis]

Did someone take notes on #174? Can you post them or email them to me?

[williamkapke]

@bnoordhuis Should we move the TSC meeting time to be more workable for you? It'd be great to have you on!

The notes are linked in the meeting notice above and the video is on YouTube. There wasn't discussion in a private session or anything.

Additionally, just to call out what you likely already know, you have the right to open issues, put them on the agenda... and even call for a vote if desired!

[bnoordhuis]

Okay, thanks. I've read to the discussion notes so I think I should be up to speed.

Apropos meeting times: a few hours earlier would be more convenient for me but is awkward for people like Rod. The current time and date is usually workable for me, it's only when my SO has social obligations that things get complicated.