Node.js Foundation Build WorkGroup Meeting 2018-02-06

[mhdawson]

Time

UTC Tue 06-Feb-2018 21:00 (09:00 PM):

Timezone	Date/Time
US / Pacific	Tue 06-Feb-2018 13:00 (01:00 PM)
US / Mountain	Tue 06-Feb-2018 14:00 (02:00 PM)
US / Central	Tue 06-Feb-2018 15:00 (03:00 PM)
US / Eastern	Tue 06-Feb-2018 16:00 (04:00 PM)
London	Tue 06-Feb-2018 21:00 (09:00 PM)
Amsterdam	Tue 06-Feb-2018 22:00 (10:00 PM)
Moscow	Wed 07-Feb-2018 00:00 (12:00 AM)
Chennai	Wed 07-Feb-2018 02:30 (02:30 AM)
Hangzhou	Wed 07-Feb-2018 05:00 (05:00 AM)
Tokyo	Wed 07-Feb-2018 06:00 (06:00 AM)
Sydney	Wed 07-Feb-2018 08:00 (08:00 AM)

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Build%20WorkGroup+Meeting+2018-02-06&iso=20180206T21
• or http://www.wolframalpha.com/input/?i=09PM+UTC%2C+Feb+06%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1zMzNvTNunkVzk6u27mm8LaMXtkm9SDPsx2-3ruBlri4/edit

Agenda

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

nodejs/build

• Security: please pay careful attention to code running through CI #1070
• CI statuses not posting #1045
• New OSX infra walkthrough #1026
• Provide read access to our ci.nodejs.org configs #972
• Remove Fedora 22, 23, 24 #962
• suggestion: investigate a commit-queue solution #705
• file and directory names for downloads #515

Invited

• Build team: @nodejs/build

Observers

Notes

The agenda comes from issues labelled with build-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

• link for participants: https://hangouts.google.com/hangouts/_/ytl/jCWBdXmo8auqQ845l8xRKZtaLeTScQ0wPszZvNgd7so=?eid=100598160817214911030
• For those who just want to watch: https://www.youtube.com/watch?v=xO1ulg6bafI
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[Trott]

@maclover7 suggested adding an agenda item about finding a way to better track tweaks, fixes, changes, etc. Right now, they end up in IRC, in this issue tracker, and probably other places (email?). Would a Trello board or using a GitHub Project or something like that help? Or maybe an extended effort to triage the issues in this repo might make the issue tracker more useful for this? I don't know. Anyway, I can make the first half of the meeting and would be happy to participate in the conversation.

[gibfahn]

@maclover7 suggested adding an agenda item about finding a way to better track tweaks, fixes, changes, etc.

Sounds good, but it would make sense to raise an issue first for discussion, and then put that on the agenda, that way we can have people not at the meeting chime in too.

[rvagg]

"finding a way to better track tweaks, fixes, changes, etc." sounds good. I've been trying to deal with the flaky Odroid C2's this week and I just changed JOBS to 2 from 4 on them under suspicion that setting it to ncpus is too much for the amount of resources (specifically memory) required and that the disk is slow enough that even with ccache doing it at 4 is not going to get much better performance. I have nowhere to note that other than on IRC, it's not really even something that goes into /ansible/ because it's a host_vars thing.

[rvagg]

Oh, and I also meant to say that I may not make this week's meeting. I'll try but I'm at a company offsite and I'm supposed to be somewhere in that time slot. Really sorry. I'll try my hardest to make it.

[mhdawson]

For discussion #1093 (comment), hopefully we'll have @rvagg to discuss.

[maclover7]

ping @mhdawson for hangouts link

[rvagg]

Who's going to lead this and set up the hangout? Sorry, I can't as I don't have much time.

[mhdawson]

Starting meeting now

[mhdawson]

https://hangouts.google.com/hangouts/_/ytl/jCWBdXmo8auqQ845l8xRKZtaLeTScQ0wPszZvNgd7so=?eid=100598160817214911030

[maclover7]

ping @mhdawson for minutes PR -- I am open to adding an agenda item discussing if we can improve this process to the next meeting