From 038b05f4cb077441e9269965ffb7754a9ac2fca7 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Wed, 25 Oct 2017 19:23:51 -0400 Subject: [PATCH 1/4] doc: add minutes for meeting Oct 25 2017 --- meetings/2017-10-25.md | 119 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 meetings/2017-10-25.md diff --git a/meetings/2017-10-25.md b/meetings/2017-10-25.md new file mode 100644 index 00000000..44f39036 --- /dev/null +++ b/meetings/2017-10-25.md @@ -0,0 +1,119 @@ +# Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-10-25 + +## Links + +* **Recording**: https://www.youtube.com/watch?v=p1LB6VxKchw +* **GitHub Issue**: https://github.com/nodejs/TSC/issues/396 +* **Minutes Google Doc**: https://docs.google.com/document/d/1ptEaqEG9sI8EhBFqZv1MQhyuEFfq1F81XyXbMqHyN84/ + +## Present + +* Anna Henningsen @addaleax (TSC) +* Colin Ihrig @cjihrig (TSC) +* Jeremiah Senkpiel @Fishrock123 (TSC) +* James M Snell @jasnell (TSC) +* Michael Dawson @mhdawson (TSC) +* Myles Borins @MylesBorins (TSC) +* Ali Ijaz Sheikh @ofrobots (TSC) +* Rod Vagg @rvagg (TSC) +* Trevor Norris @trevnorris (TSC) +* Rich Trott @Trott (TSC) +* William Kapke @williamkapke (Node.js Community Board representative) +* Forrest L Norvell @othiym23 (Moderation team member for moderation update) + +## Agenda + +## Announcements + +* Security release yesterday. There was an unrelated regression in 8.8.0 release, 8.8.1 release + being prepared today. Includes unflagging HTTP2. + +### WG update + +* Update from the moderation team (Forrest) + +* Deck used for persentation https://docs.google.com/presentation/d/1cN712pneaa7L6_wVl9-M2OpK_2Am8EbarYyoJxxyyYA/edit#slide=id.p + +* 10 members, so far have had to be intervene in 0 zeros, though there were 2 request + for guidance +* team not working group +* scope set as enforcing policies, not setting them. +* With thefourtheye joining the team now has global timezone coverage + (this has been challenge due to being a small team) +* Work coordinated through a slack workspace +* Tracy looking at training for moderation team members +* Team will suggest moderation changes, iteration based on experience gained + through events. These will come to TSC or other areas for TSC/CommComm to review. +* Myles, one thing for moderation team to think about is moderation requests + about leadership. This is something Myles would be interested to see suggestion + as to process for this (since they need to implement it). +* Forrest, as long as policy is clear enough, it should be able to be applied to + leaders and members alike. + +*Extracted from **tsc-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. + +### nodejs/node + +* Support both OpenSSL 1.1.0 and 1.0.2 [#16130](https://github.com/nodejs/node/pull/16130) + * current state is that is is getting ready to land + * not to switch, just the option to allow us to compile with 1.1 and start testing it out + * Myles had volunteered to setup a meeting, had sent out doodle. Myles may not + have bandwidth to drive this one asked if Rod can be the champion. Rod has agreed. + * Myles has already mentioned that we've had trouble getting patches landed in the openssl + project. + * Rod will take it as an action item to document the state of things and drive this to the extent + that there's anything we can do right now. + +* util,assert: expose util.isDeepStrictEqual() [#16084](https://github.com/nodejs/node/pull/16084) + * Rich, blocking objection has been removed, take off the agenda. + +* buffer: runtime-deprecate Buffer ctor by default [#15346](https://github.com/nodejs/node/pull/15346) + * Rich had action item to take pulse of TSC as there was some suggestion that maybe we + should never do it. Survey of 14 TSC memory shows there is desire to runtime deprecate + at sometime in the future. + * Remaining question is what by what criteria would it get runtime deprecation. Seems + like at this point we don't know and need to take another look in 6 months. + +* stream: move prefixed files into internal/streams. [#11957](https://github.com/nodejs/node/pull/11957) +* Enable explicit `.m.js` intent for ESM [#16170] (https://github.com/nodejs/node/pull/16170) + * remove from agenda at this. + + +### nodejs/TSC + +* Proposal to form a Governance Working Group [#383](https://github.com/nodejs/TSC/issues/383) + * James is scheduling a call. There's a [Doodle](https://doodle.com/poll/imwnmz98uad846p9) in the issue. + more TSC responses on that, please. + +* Who should be in @nodejs/security? Who should have access to the private repo? [#358](https://github.com/nodejs/TSC/issues/358) + * Myles, let's leave this to the security-wg to come up with proposal and then bring back to + TSC for review. + +### nodejs/admin + +* doc: doc expectations on TSC and CommComm members [#12](https://github.com/nodejs/admin/pull/12) + * For awareness, likely to land on Friday + * Fishrock, even though we cannot get broad values would be good for the TSC + to define a set of values for the TSC. + * Michael, agree suggested PR to start discussion on them. Don.t believe this should + block the expectations document. + * Myles doing additional values session and would like to avoid landing things + until we get that feedback. Does not believe it should block expectations doc + * William mentioned current version has removed some references to values and + believes we should not block either. + +## Q&A, Other + +* From irc, Bryan, number of uncharted WG's not an issue to have groups to + work on things which are uncharted. Michael maybe we can ask the + security-wg team to think about when/if it makes sense to request an official charter. +* Some floating moderation work that needs to be done, Myles had suggested we set up group + Across the TSC, CommComm, moderation through work edge cases. He has opened issue + and will take discussion back to the tracker. https://github.com/nodejs/admin/issues/24 + +## Upcoming Meetings + +* **Node.js Foundation Calendar**: https://nodejs.org/calendar + +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. + From 6e84d55f110e54eff601e1ccc1a7f83cdc0f9801 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 25 Oct 2017 21:06:47 -0700 Subject: [PATCH 2/4] clarification on runtime deprecation criteria question --- meetings/2017-10-25.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meetings/2017-10-25.md b/meetings/2017-10-25.md index 44f39036..436646d3 100644 --- a/meetings/2017-10-25.md +++ b/meetings/2017-10-25.md @@ -71,8 +71,9 @@ * Rich had action item to take pulse of TSC as there was some suggestion that maybe we should never do it. Survey of 14 TSC memory shows there is desire to runtime deprecate at sometime in the future. - * Remaining question is what by what criteria would it get runtime deprecation. Seems - like at this point we don't know and need to take another look in 6 months. + * Remaining question is by what criteria would it get a runtime deprecation. + Rich observed that TSC appears unwilling or unable to provide specific + criteria. * stream: move prefixed files into internal/streams. [#11957](https://github.com/nodejs/node/pull/11957) * Enable explicit `.m.js` intent for ESM [#16170] (https://github.com/nodejs/node/pull/16170) From ed7400444435ae31ffc4bedda7f71b9c4dffdc09 Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Tue, 31 Oct 2017 17:54:19 -0400 Subject: [PATCH 3/4] squash: address comments --- meetings/2017-10-25.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meetings/2017-10-25.md b/meetings/2017-10-25.md index 436646d3..62a92973 100644 --- a/meetings/2017-10-25.md +++ b/meetings/2017-10-25.md @@ -32,7 +32,7 @@ * Update from the moderation team (Forrest) -* Deck used for persentation https://docs.google.com/presentation/d/1cN712pneaa7L6_wVl9-M2OpK_2Am8EbarYyoJxxyyYA/edit#slide=id.p +* Deck used for presentation https://docs.google.com/presentation/d/1cN712pneaa7L6_wVl9-M2OpK_2Am8EbarYyoJxxyyYA/edit#slide=id.p * 10 members, so far have had to be intervene in 0 zeros, though there were 2 request for guidance @@ -55,7 +55,7 @@ ### nodejs/node * Support both OpenSSL 1.1.0 and 1.0.2 [#16130](https://github.com/nodejs/node/pull/16130) - * current state is that is is getting ready to land + * current state is that it is getting ready to land * not to switch, just the option to allow us to compile with 1.1 and start testing it out * Myles had volunteered to setup a meeting, had sent out doodle. Myles may not have bandwidth to drive this one asked if Rod can be the champion. Rod has agreed. From 3a450fd670b873305fdb8e18553df8f1cc81d85e Mon Sep 17 00:00:00 2001 From: Michael Dawson Date: Thu, 2 Nov 2017 09:29:45 -0400 Subject: [PATCH 4/4] squash: address comments --- meetings/2017-10-25.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meetings/2017-10-25.md b/meetings/2017-10-25.md index 62a92973..d371d8a3 100644 --- a/meetings/2017-10-25.md +++ b/meetings/2017-10-25.md @@ -34,12 +34,12 @@ * Deck used for presentation https://docs.google.com/presentation/d/1cN712pneaa7L6_wVl9-M2OpK_2Am8EbarYyoJxxyyYA/edit#slide=id.p -* 10 members, so far have had to be intervene in 0 zeros, though there were 2 request +* 10 members, so far have had to be intervene in 0 issues, though there were 2 requests for guidance * team not working group * scope set as enforcing policies, not setting them. * With thefourtheye joining the team now has global timezone coverage - (this has been challenge due to being a small team) + (this has been challenge due to being a small team) * Work coordinated through a slack workspace * Tracy looking at training for moderation team members * Team will suggest moderation changes, iteration based on experience gained @@ -105,7 +105,7 @@ ## Q&A, Other -* From irc, Bryan, number of uncharted WG's not an issue to have groups to +* From irc, Bryan English, number of uncharted WG's not an issue to have groups to work on things which are uncharted. Michael maybe we can ask the security-wg team to think about when/if it makes sense to request an official charter. * Some floating moderation work that needs to be done, Myles had suggested we set up group