Node.js Foundation Technical Steering Committee (TSC) Meeting 2016-08-11

[nebrius]

Node.js Foundation Technical Steering Committee (TSC) Meeting 2016-08-11

---

Time

UTC Thu 11-Aug-2016 20:00:

Timezone	Date/Time
US / Pacific	Thu 11-Aug-2016 13:00
US / Mountain	Thu 11-Aug-2016 14:00
US / Central	Thu 11-Aug-2016 15:00
US / Eastern	Thu 11-Aug-2016 16:00
Amsterdam	Thu 11-Aug-2016 22:00
Berlin	Thu 11-Aug-2016 22:00
Moscow	Thu 11-Aug-2016 23:00
Tokyo	Fri 12-Aug-2016 05:00
Sydney	Fri 12-Aug-2016 06:00

Or in your local time:

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

Links

• Minutes Google Doc: https://docs.google.com/document/d/1Sp78uVB_1NBv9AZk1pXKj-YWmwqtCA6ZqxAE_lsjuk0
• Previous Minutes Google Doc: https://docs.google.com/document/d/1ja56BVVPy946OZlDv1EQBy4TC5he6IQkQtxhE-20X4E

Agenda

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

nodejs/post-mortem

• Repositories to contribute collaboratively #30

nodejs/TSC

• TSC Board Director Elections #126
• Define "Node.js core" - Mark II #113
• Regular roll-up reporting for active working groups #109
• Define "Node.js core" #84

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)
• Julien Gilli @misterdjules (TSC)
• Mikeal Rogers @mikeal (observer/Node.js Foundation)
• Brian White @mscdex (TSC)
• Alexis Campailla @orangemocha (TSC)
• Bert Belder @piscisaureus (TSC)
• Rod Vagg @rvagg (TSC)
• Shigeki Ohtsu @shigeki (TSC)
• Trevor Norris @trevnorris (TSC)
• William Kapke @williamkapke (observer)
• Michael Dawson @mhdawson (observer)
• Anna Henningsen @addaleax (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 it.

[nebrius]

FYI I created a wiki for this repo and created a page about creating TSC meeting issues, based on what I did for this issue.

It's very similar to the CTC one, but with a couple of odds and ends changes. I'd love for people to take a look at it and see if anything doesn't seem right

[addaleax]

I’ll be there again, if nobody minds.

[mhdawson]

I'll be there

[williamkapke]

FYI I created a wiki for this repo and created a page about creating TSC meeting issues

Super awesome @nebrius! I want to automate this with the bot- if/when I do- this will be really helpful! (I'll make sure to not include that bug you mentioned)

[Trott]

@williamkapke RTYI, same thing but for CTC meetings: https://github.com/nodejs/node/wiki/Creating-a-CTC-Meeting-Issue

[misterdjules]

My apologies, I won't be able to attend today.

[williamkapke]

@nebrius , maybe update the issue to include @mhdawson & @addaleax as observers?

[nebrius]

@nebrius , maybe update the issue to include @mhdawson & @addaleax as observers?

Good call, thanks.

[nebrius]

FYI we decided to defer #121 and #122 for discussion until next time

[Fishrock123]

(or rather, until some future data when progress is made)

[bnoordhuis]

I'm afraid I have to skip today. My connection currently has 80% packet loss; browsing GH is already an exercise in patience, never mind VoIP.

[Fishrock123]

Livestream viewers, topping out at 9: