2017-12-06.md
1
# Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-12-06
2
3
## Links
4
5
* **Recording**: https://www.youtube.com/watch?v=1sHufGWR_WU
6
* **GitHub Issue**: https://github.com/nodejs/TSC/issues/432
7
* **Minutes Google Doc**: https://docs.google.com/document/d/1N029ttRxw92pv1k0Xc0-abkwbHMRW7Ts6r4nFeJbF4M
8
9
## Present
10
11
* Colin Ihrig @cjihrig (TSC)
12
* Franziska Hinkelmann @fhinkel (TSC)
13
* James M Snell @jasnell (TSC)
14
* Jeremiah Senkpiel @Fishrock123 (TSC)
15
* Matteo Collina @mcollina (TSC)
16
* Michael Dawson @mhdawson (TSC)
17
* Myles Borins @MylesBorins (TSC)
18
* Ali Sheikh @ofrobots (TSC)
19
* Rod Vagg @rvagg (TSC)
20
* Trevor Norris @trevnorris (TSC)
21
* Rich Trott @Trott (TSC)
22
* Daniel Bevenius @danbev (observer)
23
* William Kapke @williamkapke (observer)
24
25
## Agenda
26
27
### Announcements
28
29
* No announcements this week.
30
31
*Extracted from **tsc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting.
32
33
### nodejs/node
34
35
* Enable explicit `.m.js` intent for ESM [#16170](https://github.com/nodejs/node/pull/16170)
36
* asked to provide clear statement on what is negotiable and what is not
37
* Myles has been working on blog post to cover that, going out next Tuesday
38
* Myles had talked to originator of issue, discussed content, seemed easy.
39
* can remove from agenda
40
41
* buffer: runtime-deprecate Buffer(num) by default [#15608](https://github.com/nodejs/node/pull/15608)
42
* phased approach to deprecate some parts earlier
43
* question to TSC is that an option ?
44
* opinion from TSC in issue has mostly been -> not an option
45
* no opposition from those in meeting, will remove from agenda and say 'not an option' in
46
issue.
47
48
* events: add off alias to removeListener [#17156](https://github.com/nodejs/node/pull/17156)
49
* Matteo mentioned he was opposed
50
* Rod not a fan, but people seem to really want it
51
* Opposed to be it being semver minor. Believe it is a bad idea but more ok if it is
52
semver major.
53
* Trevor ran into issues in past when we added an underscore property. Cannot add to event
54
emitter lightly
55
* James, similar problems in other cases with event emitter, cases that would break
56
if somebody tried to use off on an emitter that does not extend from the event emitter
57
class.
58
* Rich Issue seems to list out issues, maybe go to vote ?
59
* Myles anyway we can land, with caveat not to backport until enough usage
60
* Matteo would like it never to go back
61
* Matteo is ok with 'do not land on 8'.
62
* James prefer semver major, land in 10. Matteo that would be even better.
63
* Jeremiah not in agreement.
64
* All in agreement that if it lands it should be semver major.
65
* Myles will put summary comment into issue.
66
67
* Add remark dependencies [#17320](https://github.com/nodejs/node/pull/17320)
68
* Added by Myles
69
* When remark was added we decided not to add the dependencies, opposition was around
70
git performance.
71
* Myles did more recent investigation found some info that it might not be a perf issue
72
* Rich, maybe we should have invited @refack to to participate in the discussion.
73
* 1800 files is about 4%
74
* Michael do we have the comparison between git clone time with/without
75
* Jeremiah, put into tarball, pull tarball and uncompress. Myles maybe we should
76
do for eslint dependencies as well. Maybe we should remove remark from test
77
suite.
78
* Refael has removed with objection.
79
* Jeremiah we should avoid pulling in many more files. Suggestion is to remove markdown
80
linting until we can find another solution
81
* James, has had enough problems that we should just remove markdown linting and then
82
fix afterwards.
83
* Myles ok with closing, need volunteer to remove linter. Will close and @refack will take point
84
on removing/finding an alternative solution. Make strategic initiative around dependency
85
management.
86
87
### nodejs/build
88
89
* note that release config is removed after 6m [#997](https://github.com/nodejs/build/pull/997)
90
* still have bits/pieces across build infra related to releases before 4.x.
91
* build team wants to remove. If we do would be pretty much impossible to build one of these
92
versions again.
93
* this to check there are no objections before we move forward.
94
* any objections if we first capture jekins xml config and put in repo. None raised.
95
96
### nodejs/TSC
97
98
* Enterprise Advisory Group [#431](https://github.com/nodejs/TSC/issues/431)
99
* Group of companies who have adopted Node.
100
* Organizing group to provide feedback
101
* Goal is to have that group run the process, that is why no other TSC members organized
102
* Feedback on priorities, pain points.
103
* Michael, how do we position versus existing user-feedback effort to put call out to companies
104
who would participate in regular interlocks.
105
* James, talk to Dan on that front.
106
* Myles, what is being done to set expectations in terms of what actions may/may not happen
107
based on input.
108
* William, important that we set expectations. user-feedback group recognizes that setting
109
expectations is important.
110
* James, top issues they mentioned were things that were already on our plates.
111
* William, feedback from these companies is good for others to see. Any chance of having
112
meetings be public.
113
* James may be a mix. Minutes were may public, but some cases were we might need to
114
have things be public.
115
* Myles what would be success metrics and how would that be different than the general
116
user-feedback outreach.
117
* Myles, should we cycle through TSC members who attend.
118
119
* Strategic Initiatives - Tracking Issue [#423](https://github.com/nodejs/TSC/issues/423)
120
* going to skip for this week
121
* asking people to do it the minutes in advance in the google doc for the meeting in case
122
we don't have time to go through them.
123
124
* HTTP/2 Initiative - There is a bit of a large cleanup on close/destroy/error semantics
125
being worked on now. It's a rather large PR that's going to be difficult to review.
126
It's not quite ready to go (gimme a few days or so). it will yield significantly improved API
127
consistency and an error flow that actually makes sense. However, if we weren't still in
128
experimental status, it would be semver-major, so just a heads up.
129
130
* New Streams API Initiative - Jeremiah and I worked through some details earlier this week.
131
We should have an updated couple of PRs in January some time.
132
133
* Moderation WG strategic initiatives update: Remaining issue to be worked out before we
134
can take this off the strategic initiatives list is how the Moderation team gets moderation
135
privileges across all the repositories. Easiest and worst solution is to make all team
136
members org owners. Better would be a bot that has certain permissions across all
137
repositories that team members can issue targeted, specific, auditable commands to.
138
Not sure how to get there from here, but without the actual power to engage in moderation
139
activities, the Moderation Team is not fully a Moderation Team.
140
141
* V8 gyp scaffolding responsibility handoff [#411](https://github.com/nodejs/TSC/issues/411)
142
* Q1, scaffolding for gyp will be removed from v8
143
* Simplest is to start checking in the scaffolding
144
* Francisca, V8 looking at getting node to build with GN, problem is might not support all
145
platforms
146
* Ben looking a cmake as an alternative
147
* Myles to take action to make this a strategic initiative.
148
149
* N-API
150
* Still working on plan to get out of experimental. Port of bcrypt is complete and
151
may be one of the modules we can get real-life usage. Push on testing and documentation
152
continues.
153
154
## Q&A, Other
155
156
No questsions this week.
157
158
## Upcoming Meetings
159
160
* **Node.js Foundation Calendar**: https://nodejs.org/calendar
161
162
Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.