Node Foundation TSC Meeting 2015-06-17

[rvagg]

Time

UTC Wed 17-Jun-15 20:00:

• San Francisco: Wed 17-Jun-15 13:00
• Amsterdam: Wed 17-Jun-15 22:00
• Moscow: Wed 17-Jun-15 23:00
• Sydney: Thu 18-Jun-15 06:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node+Foundation+TSC+Meeting+2015-06-17&iso=20150617T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+17%2C+2015+in+local+time

Links

• GitHub Issue: fs: fix fd leak in ReadStream.destroy() node#56
• Original Minutes Google Doc: https://docs.google.com/document/d/1cn7SKaKYUMYLBiQhE6HAAknnwPabKsYjpOuyQkVikW8

Attendees will be given a conference number to dial in to.

Agenda

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

nodejs/node

• Create a security team #48

nodejs/io.js

• on working with proposals from the API WG #1993

joyent/node

• Nominating new collaborators to this repository #25481
• Node should not automatically change rlimits #8704

Invited

• @bnoordhuis (TSC)
• @chrisdickinson (TSC, streams)
• @cjihrig (TSC)
• @domenic (observer)
• @Fishrock123 (TSC)
• @indutny (TSC)
• @isaacs (TSC)
• @jasnell (TSC)
• @mhdawson (TSC)
• @misterdjules (TSC)
• @mikeal (website, proposed TSC)
• @mscdex (observer, proposed TSC)
• @orangemocha (TSC)
• @piscisaureus (TSC)
• @rvagg (TSC, build)
• @shigeki (observer, proposed TSC)
• @srl295 (TSC)
• @trevnorris (TSC)

Notes

The agenda now comes from issues labelled with tsc-agenda in all 3 repositories listed above. Please label any additional issues that should be on the agenda before the meeting starts. I'm using a tool to fetch the list so it's not a big deal to collate.

This meeting will be held via Uberconference. I won't be attempting to live-stream to YouTube this time, it was too difficult last time because I had to have my microphone on. I am continuing to explore other options for broadcasing live; I don't want to completely lose that! So, there won't be a live QA on #io.js this time, very sorry, but please comment here if you have something to query.

The recording will go up on Soundcloud straight afterwards.

[bnoordhuis]

Apologies if I don't make it tonight, I have a rather tight schedule.

+1 from me on voting in Brian and Shigeki, I think they'll make great additions to the TSC.

No strong opinion on an API WG. If people want to spin up one, that's fine by me, as long as I don't have to be involved too much. :-)

[trevnorris]

@rvagg I added nodejs/node#1811 to the list. Though I also closed it because the PR was merged. The specific topic is on releasing a CVE. This may be better for the security group, but something we should get figured out.

@bnoordhuis Not getting the TSC unnecessarily involved is my plan. Most I want this group to have to do is vote on whether any API proposals are okay.

[srl295]

Back in town, should be able to make it.

[trevnorris]

Also add to the schedule, how to properly merge master branch into next.

[rvagg]

so I keep on removing the Brian and Shigeki voting thing as deferral but perhaps I shouldn't have done it this time because I've been hearing positive noises from all directions about just getting this done - let's put it back on the agenda unless there are any objections to the short notice

[rvagg]

this week's minutes: https://docs.google.com/document/d/1d4mAJgm06rpPWLDqhZcxsRnKMrS92Ip4CW2akOyeIL4