Node.js Foundation Build WorkGroup Meeting 2018-05-22

[mhdawson]

Time

UTC Tue 22-May-2018 22:00 (10:00 PM):

Timezone	Date/Time
US / Pacific	Tue 22-May-2018 15:00 (03:00 PM)
US / Mountain	Tue 22-May-2018 16:00 (04:00 PM)
US / Central	Tue 22-May-2018 17:00 (05:00 PM)
US / Eastern	Tue 22-May-2018 18:00 (06:00 PM)
London	Tue 22-May-2018 23:00 (11:00 PM)
Amsterdam	Wed 23-May-2018 00:00 (12:00 AM)
Moscow	Wed 23-May-2018 01:00 (01:00 AM)
Chennai	Wed 23-May-2018 03:30 (03:30 AM)
Hangzhou	Wed 23-May-2018 06:00 (06:00 AM)
Tokyo	Wed 23-May-2018 07:00 (07:00 AM)
Sydney	Wed 23-May-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-05-22&iso=20180522T22
• or http://www.wolframalpha.com/input/?i=10PM+UTC%2C+May+22%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1MctRKDzM_yAOawB_bvUVqcxDqqvXvQTLKjAJC604cQo/edit

Agenda

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

nodejs/build

• Use of Docker in Build CI #1226

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: Will be added a few minutes before meeting starts
• For those who just want to watch:
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[maclover7]

Unable to make it to this one, but at some point in the future can we add a "state of ansible" item? I've been doing a bunch of setup/ansible porting PRs, but there's still a bunch more architectures that need to be moved over

[mhdawson]

I'm at a conference so I'm not sure if I'll make it or not. Do we have a volunteer to chair the meeting?

[mhdawson]

@maclover7 best way to get it on the agenda would be to create a tracking issue for "state of ansible" and the tag with build-agenda. That way it will automatically be added to the agenda.

[rvagg]

I wouldn't mind skipping this one if others are unable to make it. I'm juggling a bunch of responsibilities at the moment (hence my partial absence from around here in the last couple of weeks). I also have a couple of other meetings inserted into this timeslot that I don't really want to cancel!
I'll try and drop some notes into #1277, things are more mature than they look and I think we can make some quick progress just by deleting some stuff.

[juggernaut451]

Is the call happening? As i am looking forward to join it

[Trott]

Is the call happening? As i am looking forward to join it

I think @detrohutt was looking to join or observe or something as well.

So far, it looks like I'm the only confirmed attendee among current Build WG members...

[Trott]

@nodejs/build Can everyone please apply the customary (for Build WG) 👍 to the initial post in this issue if you will attend at this time and 👎 if you need to miss this one?

Also we could probably stand to make some current Build WG members emeriti. I don't think it's a great idea to have inactive folks with elevated privileges. We can always move people back to active status if they become available to do stuff again. Having 16 people or whatever in the team makes it look like there's a lot more activity than there is. We need more active folks IMO.

[detrohutt]

@Trott I am interested in joining the meeting to discuss specific items that need additional help, but if you're the only one attending I understand if you want to use that time for something else.

[refack]

Since @rvagg's review of the new Docker usage is the only item on the agenda. I second the motion to skip this meeting.

[detrohutt]

Actually, I guess there's no reason to take up meeting time for my goal. I'll open an issue on this repo where items can be added as you think of them and I'll coordinate with the Mentorship team to try to get more help on those tasks.

[juggernaut451]

I was looking for Q/A session. As I am looking forward to joining build WG and really need help here. :(

[Trott]

@juggernaut451 My opinion only, but since many of the things that need doing require elevated privileges, the first step is to gain the trust of the Build WG. AFAIK, there's no documented procedure for that but these are the types of things that help:

• Contribute meaningfully to Node.js core.

• Participate in productive and valuable ways in the Build repo and in #node-build IRC channel.

• Demonstrate a collaborative spirit and general understanding of how the Node.js project works by participating in other working groups.

• If you happen to be employed by a company that is part of the Node.js Foundation, there's an implicit trust boost there because if you do something malicious, there would almost certainly be repercussions with your employer.

In general, if you're looking for a first working group to join, this is probably not it. It can be, but it's generally easier to get started with (for one example) the Website working group.

[maclover7]

Meeting skipped, closing this out