Repository navigation
Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-12-06 #432
Description
Time
UTC Wed 06-Dec-2017 22:00 (10:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 06-Dec-2017 14:00 (02:00 PM) |
| US / Mountain | Wed 06-Dec-2017 15:00 (03:00 PM) |
| US / Central | Wed 06-Dec-2017 16:00 (04:00 PM) |
| US / Eastern | Wed 06-Dec-2017 17:00 (05:00 PM) |
| Amsterdam | Wed 06-Dec-2017 23:00 (11:00 PM) |
| Moscow | Thu 07-Dec-2017 01:00 (01:00 AM) |
| Chennai | Thu 07-Dec-2017 03:30 (03:30 AM) |
| Hangzhou | Thu 07-Dec-2017 06:00 (06:00 AM) |
| Tokyo | Thu 07-Dec-2017 07:00 (07:00 AM) |
| Sydney | Thu 07-Dec-2017 09:00 (09:00 AM) |
Or in your local time:
- http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2017-12-06&iso=20171206T22
- or http://www.wolframalpha.com/input/?i=10pm+UTC%2C+Dec+06%2C+2017+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1N029ttRxw92pv1k0Xc0-abkwbHMRW7Ts6r4nFeJbF4M/edit
Agenda
Extracted from TSC-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- Enable explicit
.m.jsintent for ESM #16170 - buffer: runtime-deprecate Buffer(num) by default #15608
- events: add off alias to removeListener #17156
- Add remark dependencies #17320
nodejs/build
- note that release config is removed after 6m #997
nodejs/TSC
- Enterprise Advisory Group #431
- Strategic Initiatives - Tracking Issue #423
- V8 gyp scaffolding responsibility handoff #411
Invited
- Anna Henningsen @addaleax (TSC)
- Сковорода Никита Андреевич @ChALkeR (TSC)
- Colin Ihrig @cjihrig (TSC)
- Evan Lucas @evanlucas (TSC)
- Franziska Hinkelmann @fhinkel (TSC)
- Jeremiah Senkpiel @Fishrock123 (TSC)
- Josh Gavant @joshgav (TSC)
- Fedor Indutny @indutny (TSC)
- James M Snell @jasnell (TSC)
- Joyee Cheung @joyeecheung (TSC)
- Matteo Collina @mcollina (TSC)
- Michael Dawson @mhdawson (TSC)
- Brian White @mscdex (TSC)
- Myles Borins @MylesBorins (TSC)
- Ali Ijaz Sheikh @ofrobots (TSC)
- Rod Vagg @rvagg (TSC)
- Michaël Zasso @targos (TSC)
- Sakthipriyan Vairamani @thefourtheye (TSC)
- Trevor Norris @trevnorris (TSC)
- Rich Trott @Trott (TSC)
Observers
- Daniel Bevenius @danbev
- William Kapke @williamkapke
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
Uberconference; participants should have the link & numbers, contact me if you don't.
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
Activity
Trott commentedon Dec 4, 2017
Adding @williamkapke and @danbev as observers.
Trott commentedon Dec 4, 2017
The thing to do on that one is publish that doc that @MylesBorins has been shepherding.
This can be removed if there is consensus about what @addaleax and @ChALkeR wrote that it does not seem to make sense to deprecate
Buffer(number)separately fromBufer(string). In other words, if and when Buffer constructor is runtime deprecated, both of those forms will be runtime deprecated at the same time.Should a litmus test for strategic initiatives be something that will someday not be strategic anymore? LIke, I imagine at some point we won't need weekly updates on
http2anymore. So that makes sense to me to have it on there. In contrast, I'm not typically going to have much to say about onboarding other than "so-and-so got onboarded, and here's who's next" which doesn't seem very strategic. I think I and others may have conflated "strategic" with "important" when making that list. Maybe everything important doesn't need to be on that list.Trott commentedon Dec 4, 2017
I'll move this conversation to that issue.
Trott commentedon Dec 4, 2017
I removed
tsc-reviewfrom 5 issues. You're welcome. There are still 11 issues labeldtsc-review. 😱 @nodejs/tsc, please review! https://github.com/search?o=desc&q=org%3Anodejs+label%3Atsc-review&s=&type=Issues&utf8=%E2%9C%93I'll call special attention to three of them:
This ES Modules one seems like it's something that ought to get a resolution: Regression: Resolution algorithm collision node#14990
This
Buffer,isEncoding()one is quite old and seems to be something that should be resolvable. Buffer.isEncoding regards an empty string as a valid encoding node#9654Joyee tagged this one 12 days ago but only one other TSC member has dropped by to comment. errors: should we raise assersions for type checks in process.bindings? node#17244
MylesBorins commentedon Dec 4, 2017
Can we please add nodejs/node#17320 to the agenda
MylesBorins commentedon Dec 4, 2017
@mcollina are you back for this meeting? If so we should add nodejs/node#17156 to the agenda
mcollina commentedon Dec 4, 2017
I will be joining this meeting!
Trott commentedon Dec 4, 2017
@MylesBorins and anyone else on the TSC: I think it's safe to assume that @mhdawson would be happy for you or any other TSC member to add stuff to the agenda yourself with the following easy three-steps:
I don't think you need to ask Michael or anyone else to do it and, in fact, I suspect he'd prefer you save him the trouble that way.
(And if I'm wrong, then @mhdawson should correct me so that I stop doing that, because that's how I handle it. :-D )
rvagg commentedon Dec 5, 2017
I'll be there for the meeting but want to register that I'm currently travelling, this week and last, and am less engaged than my current norm (which is admittedly not highly engaged outside of Build), so have missed a few discussions I was roped in to and haven't had time to look over the tsc-review items. Apologies!
MylesBorins commentedon Dec 5, 2017
I've added #411 to the agenda "V8 gyp scaffolding responsibility handoff"
Have a quick update on this
mhdawson commentedon Dec 5, 2017
@Trott thanks for your comment. I'm happy to have people to add to agenda as outlined (actually very happy)
mhdawson commentedon Dec 5, 2017
Updated links for "in your local time" seems like they have been being generated incorrectly since we started rotating times.
targos commentedon Dec 6, 2017
My apologies, I will have to miss this one. I'm not feeling good and it's late.
evanlucas commentedon Dec 6, 2017
Apologies, I won't be able to make it today. I'll look through the marked issues this afternoon though.
rvagg commentedon Dec 6, 2017
FYI I've found a setting in Uberconference to not record calls automatically so I've flipped that. Since nobody else has access to recordings and I haven't even looked at them since back when we published them to Soundcloud (!) I'm guessing that it'd be preferable to not record, particularly for the private business parts. Since we are broadcasting to YouTube we have recordings of public portions.
Trott commentedon Dec 6, 2017
@nodejs/tsc Please find the spot in the Google Doc to add your strategic initiatives update, and add an update there for any strategic initiatives for which you are the champion. Thanks!
mhdawson commentedon Dec 7, 2017
@nodejs/tsc to add on to @Trott comment. This is an ongoing ask. We'd like an update to be added each week before the meeting, even if you can't make the meeting itself.
mhdawson commentedon Dec 7, 2017
PR for minutes: #434