LTS WG Meeting 17 July 2017

[mhdawson]

I see by the schedule the meeting is set for today. @gibfahn has been raising the issues lately but he is on vacation for a few weeks so I'm opening this one now (better late than never).

Present

@nodejs/lts, maybe @nodejs/release if they're interested

When

9PM Monday July 17th UTC, or in your local timezone:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+LTS+Working+Group+Meeting&iso=20170626T17&p1=179&ah=1

Previous meetings: #233

Where

Hangouts on Air:

• Observers
• [Participants] (will be added a few minutes before meeting starts)
• Events page
• Minutes

Agenda

nodejs/node

• CI: test with --with-snapshot on the slower platforms #14222
• tracking issue: full VS2017 support #13052
• (v6.x backport) src: allow CLI args in env with NODE_OPTIONS #12677
• inspector: enable --inspect-brk in v6 #12615
• Remove indexOf usage from tests in favor of includes #12586

nodejs/LTS

• doc: charter the Release working group #223

nodejs/CTC

• Chartering the Release Team as a Working Group #123
• meta: charter the LTS Working Group #122

Any questions in #node-dev on IRC or comments in this thread

Please 👍 if you can make the meeting, and 👎 if you cannot.

[MylesBorins]

Most of those issues are voting on semver minor changes I'm going to suggest we skip this week if no one is opposed

…

On Jul 17, 2017 9:22 AM, "Michael Dawson" ***@***.***> wrote: I see by the schedule the meeting is set for today. @gibfahn <https://github.com/gibfahn> has been raising the issues lately but he is on vacation for a few weeks so I'm opening this one now (better late than never). Present @nodejs/lts <https://github.com/orgs/nodejs/teams/lts>, maybe @nodejs/release <https://github.com/orgs/nodejs/teams/release> if they're interested When 9PM Monday July 17th UTC, or in your local timezone: https://www.timeanddate.com/worldclock/fixedtime.html?msg= Node.js+LTS+Working+Group+Meeting&iso=20170626T17&p1=179&ah=1 Previous meetings: #233 <#233> Where Hangouts on Air: - Observers - [Participants] () - Events page <https://www.youtube.com/my_live_events> - Minutes <https://docs.google.com/document/d/16c_FvWTi-IJ-gZkjfo_eQtIOyRpgpGRUGTq2re3CnGs/edit?usp=sharing> Agenda nodejs/node - CI: test with --with-snapshot on the slower platforms #14222 <nodejs/node#14222> - tracking issue: full VS2017 support #13052 <nodejs/node#13052> - (v6.x backport) src: allow CLI args in env with NODE_OPTIONS #12677 <nodejs/node#12677> - inspector: enable --inspect-brk in v6 #12615 <nodejs/node#12615> - Remove indexOf usage from tests in favor of includes #12586 <nodejs/node#12586> nodejs/LTS - doc: charter the Release working group #223 <#223> nodejs/CTC - Chartering the Release Team as a Working Group #123 <nodejs/CTC#123> - meta: charter the LTS Working Group #122 <nodejs/CTC#122> *Any questions in #node-dev on IRC or comments in this thread* Please 👍 if you can make the meeting, and 👎 if you cannot. — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#235>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecVzQt2fICEJGvJai9lPIZVm6tCgS2ks5sO2ADgaJpZM4OZ9sy> .

[sam-github]

I can make the time, but skipping seems reasonable, if we all comment on those issues in github.

[mhdawson]

I'd really like to get to closure on #223 if we are agreed that we are ready to go (assigned for CTC review/approval) modulo last remaining nits, I think we can cancel, otherwise I think we should have a conversation in the meeting to get agreement on what else needs to change.

[sam-github]

I don't have any comment on #223, it LGTM. Though I don't understand why every WG needs to rediscuss the boilerplate (CONTRIBUTING.md, etc), it seems like they should be the same for all WGs. If all the comments have been addressed, can't it just be landed?

[MylesBorins]

I've just put my notes on #223
Overall looks v good, just a handful of nits. I don't think having the meeting is going to help flesh it out any further than it currently is... but more than happy to attend

[mhdawson]

@MylesBorins thanks, I'll push an update to address the new comments and then I'd like to add to the agenda for the CI.

I'll cancel the meeting for today.