Repository navigation
Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-05-08 #700
Description
Time
UTC Wed 08-May-2019 16:00 (04:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 08-May-2019 09:00 (09:00 AM) |
| US / Mountain | Wed 08-May-2019 10:00 (10:00 AM) |
| US / Central | Wed 08-May-2019 11:00 (11:00 AM) |
| US / Eastern | Wed 08-May-2019 12:00 (12:00 PM) |
| London | Wed 08-May-2019 17:00 (05:00 PM) |
| Amsterdam | Wed 08-May-2019 18:00 (06:00 PM) |
| Moscow | Wed 08-May-2019 19:00 (07:00 PM) |
| Chennai | Wed 08-May-2019 21:30 (09:30 PM) |
| Hangzhou | Thu 09-May-2019 00:00 (12:00 AM) |
| Tokyo | Thu 09-May-2019 01:00 (01:00 AM) |
| Sydney | Thu 09-May-2019 02:00 (02: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-05-08&iso=20190508T16
- or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+May+08%2C+2019+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1waCOj9uS5ByqAJXFldeBsSEUsSS9sBEJbmUMS-CSSiE/edit
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- benchmark: refactor buffer benchmarks #26418
nodejs/TSC
- Nominating Sam Roberts (@sam-github) to the TSC #687
- Tracking issue for updating TSC on Board Meetings #476
- Strategic Initiatives - Tracking Issue #423
Invited
- Anna Henningsen @addaleax (TSC)
- Anatoli Papirovski @apapirovski (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)
- Rod Vagg @rvagg (TSC)
- Michaël Zasso @targos (TSC)
- Sakthipriyan Vairamani @thefourtheye (TSC)
- Rich Trott @Trott (TSC)
Observers/Guests
- Sam Roberts @sam-github (observer)
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
jasnell commentedon May 7, 2019
I'll be unavailable this week due to a schedule conflict.
Trott commentedon May 7, 2019
Maybe cancel? This is shaping up to perhaps be another low-attendance, light-agenda meeting. (I think it's a sign of health that the TSC meeting is canceled frequently, as long as agenda items aren't piling up. If we have more important things to do than meeting for the sake of meeting, and if we're taking care of things in the issue tracker or elsewhere, that's great.)
Trott commentedon May 7, 2019
One of the two non-standing items on the agenda is nominating Sam. This is nearly approved in #687, needing just another two or three (I didn't count) @nodejs/tsc +1's to be done. If that happens, then doing it in the meeting as a formality only. I'd be OK with calling it good, adding him, and announcing it in the announcements segment of the next meeting, whenever that is.
If anyone on @nodejs/tsc has reservations about adding Sam at this time, putting those reservations in the issue or else emailing the TSC mailing list about it would be prudent.
Trott commentedon May 7, 2019
The other item on the agenda that isn't a standing item is nodejs/node#26418. That absolutely needs more @nodejs/tsc attention as there have been zero TSC participants thus far. Go over there, read up, and comment, even if it's to say you have no opinion! At least that let's everyone know you're not ignoring it and that you don't need to be consulted if a contentious decision comes down to a vote.
mhdawson commentedon May 8, 2019
I'd be in favor of cancelling.
On the nomination for Sam we now have 10/18 +1s and no objections.
On #26418 it would be good to have some discussion, but making sure people are thinking about it and then talking about it at the next meeting might make the most sense.
mhdawson commentedon May 8, 2019
Any objections to cancelling, if I don't see any by tomorrow morning at 9EST I'll go ahead and cancel.
apapirovski commentedon May 8, 2019
I'm in favor of cancelling. The benchmark issue can be discussed on Github first.
Trott commentedon May 8, 2019
Closing/cancelling per offline request/instructions from @mhdawson.