Node.js Technical Steering Committee, 13 Dec 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2017-12-13 Node.js Foundation Technical Steering Committee (TSC) Meeting

Description

https://github.com/nodejs/TSC/issues/435

A

Hello and welcome to the node.js foundation technical steering committee meeting on December 13th 2017 I think we can start off with announcements. I have want to make its issue 56. In the summit repository, we are planning a collaboration summit in Berlin right before J's confit you and as far as it looks right now. This will probably happen on May 31st and Friday June 1st. The we haven't figured out the details yet, but this is most likely the fixed dates, mostly organized by Tracy Matteo, Gianni and Dee Shaw.

A

So if you have to add anything, look at the 56 issue.

A

Okay, then, we have a few issues with TSE agenda. The first one is one: seven, one, five, six rich added that it's the alias for off for the listener rich. You want to say something about that.

B

A

Thought when I checked earlier, there was actually enough pluses, but maybe I'm confusing it yeah moving it to next week sounds good to me.

A

A

A

Yes, please thank you, okay, then. The next issue is a module change by Bradley one five, zero one, five Ruben added this to the agenda. Did anyone else? Have a look at this.

A

So I actually didn't see any explicit ones in there, and there are a few approvals. I would say we kick it back to the issue tracker and finish it. There.

A

Well, Michael says: I think we need to wait for an update from Bradley. That sounds reasonable.

A

Okay, I suggest we leave those on github and ping Bradley if he wants to add anything to it and then pick it up after his update.

A

Yes and Richards suggested that we invite Bradley if we discuss it next week. That sounds reason Oh. Anybody wants to take this as an action item. If not, I can also do that.

A

Okay, then, the next issue is one four, seven, nine five, it's a change by Gibson and also Ruben added this to the agenda. One four, seven, nine five.

A

It's about updating the minimum kernel version and also a change to G Lib C.

A

And I think we should figure out if we want to land this on 10:00 or later.

A

I've seen sorry.

A

Yeah, that seems reasonable. Otherwise we have issues on here and no context to talk about them.

A

So, depending on whether this in the last issue, if we still have them on the agenda next week, we can decide if I want to invite Ruben for them.

A

Okay, so we wait till we have more people and maybe Reuben and Gibson, then moving on to the TSC issues, four to three that's days: strategic initiatives.

A

Basically our little stand up and I think Michael Dawson has left a comment here about NRP continue to work on moving out of experimental, looking to use bcrypt and one of Anna's modules for production use have made some progress on investigating. How note pre job will work, focus on tests and dark continues.

A

Who I was just updating something here? Do you want to talk a lot? Do you.

A

Okay, thanks rich and then I'm assuming this is Michael writing here. V8 open, pull request for v8 six for not expecting major issues. That's good.

A

Should we go over the other initiatives or anybody from the other initiatives present? Who would like to say something? I see the first one. The second one is modules. I, think everybody saw the blog post on the node.js foundation, medium publication, about modules.

A

Then the next issue is the TC nomination of Danielle. The venues for 1/9 rich made the nomination and it had overwhelmingly positive support on the issue. Tracker I, don't know if we can finalize this in the meeting or if we should wait for meeting with more people present.

A

Okay, well, if you're listening, Danielle will come on board very soon. Yes,.

A

A

Okay, then, the next issue put it on the agenda document: guidelines for accountability, expectations for all members of the TSC and calm calm. This was opened by Michael Dawson and we should discuss the next steps again. I think we want to move this to next week.

A

All right and then the next one is the.

A

Tac issue, one seven, eight that was opened in 2015 by Sam miles added it because he wanted to discuss. If we should work on this, some more or if we can close this I, don't know if anybody wants to have a look at it right now, I would vote for closing it because it's been open for so long and our documents have changed and we could open a more targeted issue any time it's needed.

A

A

If nobody here objects, I'll go ahead and close it after the meeting, we can always reopen it since we are somewhat in a minority today,.

A

Okay, that's all the points we had on the agenda so far. Thank you rich for taking notes. Is there any Q&A on the stream.

A

Okay, nobody can hear anybody except me in the stream- that's a shame, but then the only one talking is rich.

A

Okay and I have to figure out how to change this mic setup the next time, but it's mostly just me talking anyway, so you didn't miss too much. Sorry, everybody we'll we'll figure out technology. The next time.

A

Okay, upcoming meetings later today, there's the moderation meeting the rich mentioned. There's also the diagnostics working group meeting and the next TSC meeting is next week on December 20th have a look at the note calendar to have all the meetings in the right time zone and unless anybody else has anything I think that's it today, for the public part.

A

Thanks everybody for listening to just me, bye, bye,.