Repository navigation
Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-10-09 #764
Description
Time
UTC Wed 09-Oct-2019 20:00 (08:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 09-Oct-2019 13:00 (01:00 PM) |
| US / Mountain | Wed 09-Oct-2019 14:00 (02:00 PM) |
| US / Central | Wed 09-Oct-2019 15:00 (03:00 PM) |
| US / Eastern | Wed 09-Oct-2019 16:00 (04:00 PM) |
| London | Wed 09-Oct-2019 21:00 (09:00 PM) |
| Amsterdam | Wed 09-Oct-2019 22:00 (10:00 PM) |
| Moscow | Wed 09-Oct-2019 23:00 (11:00 PM) |
| Chennai | Thu 10-Oct-2019 01:30 (01:30 AM) |
| Hangzhou | Thu 10-Oct-2019 04:00 (04:00 AM) |
| Tokyo | Thu 10-Oct-2019 05:00 (05:00 AM) |
| Sydney | Thu 10-Oct-2019 07:00 (07:00 AM) |
Or in your local time:
- http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2019-10-09&iso=20191009T20
- or http://www.wolframalpha.com/input/?i=08PM+UTC%2C+Oct+09%2C+2019+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1ICux0B8Py9xpxpRPJ26418_mw5OpU2KoTxhkUnnNk10/edit
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- build: ongoing list of actions for Python 3 compatibility #25789
nodejs/TSC
- decharter website working group #761
nodejs/admin
- Transfer jenkins CI tool tap2junit into Node.js org #413
Invited
- Anna Henningsen @addaleax (TSC)
- Anatoli Papirovski @apapirovski (TSC)
- Beth Griggs @BethGriggs (TSC)
- Сковорода Никита Андреевич @ChALkeR (TSC)
- Colin Ihrig @cjihrig (TSC)
- Daniel Bevenius @danbev (TSC)
- Franziska Hinkelmann @fhinkel (TSC)
- Jeremiah Senkpiel @Fishrock123 (TSC)
- Gabriel Schulhof @gabrielschulhof (TSC)
- Gireesh Punathil @gireeshpunathil (TSC)
- James Snell @jasnell (TSC)
- Joyee Cheung @joyeecheung (TSC)
- Matteo Collina @mcollina (TSC)
- Michael Dawson @mhdawson (TSC)
- Myles Borins @MylesBorins (TSC)
- Sam Roberts @sam-github (TSC)
- Michaël Zasso @targos (TSC)
- Sakthipriyan Vairamani @thefourtheye (TSC)
- Tobias Nießen @tniessen (TSC)
- Rich Trott @Trott (TSC)
Observers/Guests
- Christian Clauss @cclauss (guest participant)
Notes
The agenda comes from issues labelled with tsc-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
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.
- 👍 - Attending
- 👎 - Not attending
- 😕 - Not sure yet
Activity
Trott commentedon Oct 8, 2019
#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.
sam-github commentedon Oct 8, 2019
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.
richardlau commentedon Oct 8, 2019
nodejs/node#29885
mhdawson commentedon Oct 8, 2019
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?
rvagg commentedon Oct 9, 2019
So it looks like npm opted to pick up our node-gyp@5.0.5 release rather than the node-gyp@6.0.0, 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
v5.xbranch while npm@6 continues to live. That's not ideal but shouldn't be a big deal, we just have to remember to go through the motions of backporting and releasing.sam-github commentedon Oct 9, 2019
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.
cc: npm/cli#260 (comment)
mhdawson commentedon Oct 9, 2019
Seems to be consensus to cancel. Cancelling and removing from calendar.