Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-10-09 #764
Comments
|
#761 (decharter website working group) has landed and can be removed from the agenda, although I suppose it can be left on for announcement/awareness purposes. |
|
nodejs/tap2junit#18 is in progress, and updates tap13.py to an Apache licensed version, just needs a bit of help, not sure it needs TSC discussion python progress is basically that npm/cli#260 (comment) has landed on master, so we are now waiting for npm to get released and re-vendored. Should be in next couple days. |
|
|
Given that the items on the agenda seem to have been handled in github and don't need discussion in a meeting this week I'm going to suggest we cancel again this week. @nodejs/tsc any objections or additional agenda items? |
So it looks like npm opted to pick up our [email protected] release rather than the [email protected], which probably shouldn't be a surprise because it is technically breaking. See https://github.com/nodejs/node-gyp/blob/master/CHANGELOG.md#v600-2019-10-04 — the two main things that we did in v6 were (1) selecting Python 3 ahead of 2 where both are available (v5 does the reverse) and (2) properly drop support for the ancient Python 2.6 (which has untested support and it'd be amazing if there was much use of it anyway). My guess is that they're opting to keep npm@6 on node-gyp@5, so that tells us we'll need to continue maintaining our new |
|
I don't pretend to read minds, but I'm pretty sure that they picked up 5.0.4 because @cclauss reached out to @issacs in PM over slack and asked him to do that specifically. He bumped to 5.0.5 because it got released a while later before the bump to 5.0.4 landed. I wouldn't interpret it as a long-term policy position. Once we've got this support released in 13.x, and some suggestions that it is working for people, I don't anticipate difficulties in convincing them that bumping to node-gyp@6 in the npm@6 line is safe. |
|
Seems to be consensus to cancel. Cancelling and removing from calendar. |
Time
UTC Wed 09-Oct-2019 20:00 (08:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/TSC
nodejs/admin
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: