doc: add minutes for meeting Sep 13 2017 #349
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,151 @@ | ||
| # Node Foundation TSC Meeting 2017-09-13 | ||
| ## Links | ||
|
|
||
| * **Recording**: * **GitHub Issue**: [TSC#338](https://github.com/nodejs/TSC/issues/388) | ||
| * **Minutes Google Doc**: https://docs.google.com/document/d/1tOeEpEz2Qf7ybjsoFXRrMSpNrEcKIIfnc3eqDYeP0zU/edit?usp=sharing | ||
| * _Previous Minutes Google Doc: <https://docs.google.com/document/d/1al5l33g9wlNS3fMQHNdpxyhWPoJhLAMtu4ChaAiCmYs>_ | ||
|
|
||
| ## Present | ||
|
|
||
| * Ali Ijaz Sheikh @ofrobots (TSC) | ||
| * Anna Henningsen @addaleax (TSC) | ||
| * Brian White @mscdex (TSC) | ||
| * Сковорода Никита Андреевич @ChALkeR (TSC) | ||
| * Colin Ihrig @cjihrig (TSC) | ||
| * Evan Lucas @evanlucas (TSC) | ||
| * Jeremiah Senkpiel @Fishrock123 (TS | ||
| * James M Snell @jasnell (TSC) | ||
| * Myles Borins @MylesBorins (TSC) | ||
| * Matteo Collina @mcollina (TSC) | ||
| * Michael Dawson @mhdawson (TSC) | ||
| * Michaël Zasso @targos (TSC) | ||
| * Rich Trott @Trott (TSC) | ||
| * Rod Vagg @rvagg (TSC) | ||
| * Sakthipriyan Vairamani @thefourtheye (TSC) | ||
| * William Kapke @williamkapke (Observer) | ||
|
|
||
| ## Agenda | ||
|
|
||
| * announcements | ||
|
|
||
| * review previous meeting | ||
|
|
||
| ### nodejs/TSC | ||
|
|
||
| * New TSC Director/Chair Elections [#326](https://github.com/nodejs/TSC/issues/326) | ||
| * TSC Meeting Schedule [#336](https://github.com/nodejs/TSC/issues/336) | ||
| * 2FA for the entire org [#301](https://github.com/nodejs/TSC/issues/301) | ||
| * Candidate "areas" for TSC and Community Committee [#278](https://github.com/nodejs/TSC/issues/278) | ||
| * Copyright Date [#195](https://github.com/nodejs/TSC/issues/195) | ||
| * Regular roll-up reporting for active working groups [#109](https://github.com/nodejs/TSC/issues/109) | ||
|
|
||
| ### nodejs/node | ||
|
|
||
| * stream: remove {writeableState/readableState}.length [#12857](https://github.com/nodejs/node/pull/12857) | ||
| * Cleanup `_writableState` and `_readableState` access across codebase [#445](https://github.com/nodejs/node/issues/445) | ||
|
|
||
| ### nodejs/CTC | ||
|
|
||
| * Requesting Rod to step down or be removed from the CTC [#165](https://github.com/nodejs/CTC/issues/165) | ||
|
|
||
| ## Announcements | ||
|
|
||
| No announcements this week. | ||
|
|
||
| ## Previous Meeting Review | ||
|
|
||
| We skipped this as we had a packed agenda. | ||
|
|
||
| ## Minutes | ||
|
|
||
| ### nodejs/TSC | ||
| * New TSC Director/Chair Elections [#326](https://github.com/nodejs/TSC/issues/326) | ||
| * No objections, Myles acclaimed as Directory, Michael acclaimed as Chair | ||
|
|
||
| * TSC Meeting Schedule [#336](https://github.com/nodejs/TSC/issues/336) | ||
| * We should revisit quarterly, ideally aligned with | ||
| daylight savings times changes. | ||
| * Agreed we should move forward with the proposed times. | ||
|
|
||
| * 2FA for the entire org [#301](https://github.com/nodejs/TSC/issues/301) | ||
| * We have consensus on step 1, will take of agenda. | ||
|
There was a problem hiding this comment. I always get confused, is it |
||
| * Myles, explore usb keys, could foundation fund ? | ||
| * Rich, is has not been an issue so far, can we defer until we see | ||
|
|
||
| if it will be an issue. | ||
| * Matteo, biggest issue is telling and reminding people to do it. | ||
| * Matteo, would be good to have policy that if you need financial | ||
| support you can request it. | ||
|
|
||
| * Candidate "areas" for TSC and Community Committee [#278](https://github.com/nodejs/TSC/issues/278) | ||
| * Michael gave overview and request to get involved in issue | ||
| * Mateo highlighted Metrics as one where we might do more. | ||
|
|
||
|
|
||
| * Copyright Date [#195](https://github.com/nodejs/TSC/issues/195) | ||
| * Myles to bring up at one board meeting | ||
| * Remove from TSC agenda. | ||
|
|
||
| * Regular roll-up reporting for active working groups [#109](https://github.com/nodejs/TSC/issues/109) | ||
| * Myles is going to try to get podcast style updates going. | ||
|
|
||
|
|
||
| ### nodejs/node | ||
|
|
||
| * stream: remove {writeableState/readableState}.length [#12857](https://github.com/nodejs/node/pull/12857) | ||
| * tied to 445, see discussion there | ||
|
|
||
| * Cleanup `_writableState` and `_readableState` access across codebase [#445](https://github.com/nodejs/node/issues/445) | ||
| * prefer not to tack on properties to people’s object | ||
| * having bundled into separate objects is better | ||
| * anna, Brian are you ok with current state ? | ||
| * Brian, _ not ideal but if we can’t agree on any alternatives yes | ||
| * Can’t explain how it works without including discussions of | ||
| internal state machine. | ||
| * If we have separate object that refers to existing one, but | ||
| Matteo believes this may be an issue due to additional allocation | ||
| * Jeremiah just consider _XX for writable and readable part of | ||
|
There was a problem hiding this comment. Nit: I think the There was a problem hiding this comment. I looked at in "view" and it seemed ok. |
||
| public API and doc. Brian does not prefer this but if not other | ||
| good solutions then keep as is. | ||
| * Matteo, fine to close all issues, but has been requested in | ||
| the past, or somebody proposes alternative. | ||
| * Matteo, time to close so let's have a vote ? | ||
| * Myles, form interest group with Matteo, Brian, Anna, Jeremiah | ||
| * Rich, possibly just at impasse, calling for vote | ||
| * Matteo will open an issue to collect votes. | ||
|
|
||
| # deps: backport V8 update to 6.1 https://github.com/nodejs/node/pull/15393 | ||
| * Land 6.1 into 8 LTS | ||
| * V8 team has worked on abi compatible patches (unclear if this | ||
| is complete yet) | ||
| * V8 reports that 6.1 has a larger number of fixes that would help | ||
| ongoing maintenance | ||
| * Rod, originally we said 2 months at one point | ||
| * We would need to set end Oct at LTS release date | ||
|
There was a problem hiding this comment. Nit: as LTS release date? |
||
| * Research this week on risk/reward and push decision to LTS/Release | ||
| working group for informed decision on upcoming Monday LTS/Release meeting | ||
|
|
||
| ### nodejs/security-wg | ||
|
|
||
| * CVE management process for Node.js [#33](https://github.com/nodejs/security-wg/issues/33) | ||
| * Michael gave an overview of the proposal. Wanted to make sure TSC | ||
| was comfortable moving forward. | ||
| * We agreed to leave on agenda, take discussion back to github | ||
| for 1 week and discuss in the meeting gnext week. | ||
|
|
||
|
|
||
| ### nodejs/CTC | ||
|
|
||
| * Requesting Rod to step down or be removed from the CTC [#165](https://github.com/nodejs/CTC/issues/165) | ||
| * Ongoing discussion over last week | ||
| * Most appropriate to discuss next steps in private section of meeting | ||
|
|
||
| ## Q&A, Other | ||
|
|
||
| * not seen simple user access control with react ? | ||
| * we are not sure what the questions is. | ||
| * try using the help nodejs/repo | ||
|
There was a problem hiding this comment. Nit: nodejs/help repo |
||
|
|
||
| ## Upcoming Meetings | ||
|
|
||
| * **Node.js Foundation Calendar**: https://nodejs.org/calendar | ||
|
|
||
| Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Director
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be better to have it as Michael Dawson, as we had Michaël and Michael in the meeting today?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
acclaimedis the wrong verb here. (It means praised.) I thinknamedwould be a better word choice. @mhdawson Would you prefer we push nits like that ourselves, or do you prefer to handle them so you can evaluate them?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Full names or else GitHub handles seem like the way to go to avoid ambiguity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with people pushing the nits themselves.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed