doc: add minutes for meeting 9 July 2020 (#891)

* doc: add minutes for meeting 9 July 2020

Signed-off-by: Michael Dawson <michael_dawson@ca.ibm.com>

meetings/2020-07-09.md

@@ -0,0 +1,80 @@
+# Node.js Technical Steering Committee (TSC) Meeting 2020-07-09
+
+## Links
+
+* **Recording**:  https://youtu.be/QSJHvgI0oAI
+* **GitHub Issue**: https://github.com/nodejs/TSC/issues/890
+
+## Present
+
+* Anna Henningsen @addaleax (TSC)
+* Beth Griggs @BethGriggs (TSC)
+* Ruben Bridgewater @BridgeAR (TSC)
+* Colin Ihrig @cjihrig (TSC)
+* Shelley Vohr @codebytere (TSC)
+* Daniel Bevenius @danbev (TSC)
+* Gireesh Punathil @gireeshpunathil (TSC)
+* Matheus Marchini @mmarchini (TSC)
+* Michael Dawson @mhdawson (TSC)
+* Tobias Nießen @tniessen (TSC)
+* Rich Trott @Trott (TSC)
+
+## Agenda
+
+### Announcements
+
+* Kickoff of “Next 10 years of Node.js” at collab summit, follow on: [#34260](https://github.com/nodejs/node/issues/34260)
+
+* A number of collaborator nominations that have been approved and 3 in flight. For details 
+  check out: https://github.com/nodejs/TSC/issues/890#issuecomment-654929527
+
+
+### CPC and Board Meeting Updates
+
+*Extracted from **tsc-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting.
+
+
+### nodejs/node
+
+* Proposal: create a triage team to manage the backlog [#34054](https://github.com/nodejs/node/issues/34054)
+  * From collab summit discussion, suggestion of triage team 
+    * have been trying out in the Express repo with good success
+    * people can request to become a triager, that then lets them help tag, help manage
+      issues.
+    * it provides another way that people can help without being collaborator
+    * Rich, does this require write access?
+    * Gireesh, no uses the triage role which has more limited access (tag, open/close issues)
+    * Individual efforts are hard to sustain
+    * If TSC agrees, next step would be to provide space for team collaboration (slack channel, 
+      get togethers, etc.)
+    * No objections, or concerns a few Sounds good
+    * Michael next step is PR to add role to governance/docs.
+
+* Rename default branch from "master" to "main" or something similar [#33864](https://github.com/nodejs/node/issues/33864)
+  * Discussed last week.  Waiting for tooling/pattern from Github or elsewhere before moving
+     forward.
+
+* bootstrap: include bootstrapped Environment in builtin snapshot  [#32984](https://github.com/nodejs/node/pull/32984)
+  * Has been discussed a few times, but we’re not helping to resolve
+  * Dan possible to have one approach for internal/Node.js use and then a different one
+    for user code.
+  * Anna, think that is what Joyee is advocating.
+  * Dan will try to take some time next week to take a closer look.
+
+### nodejs/admin
+
+
+* Audit Google account access [#389](https://github.com/nodejs/admin/issues/389)
+
+## Strategic Initiatives
+
+* build resources
+  * one past significant contributor is finding more time, yay!
+  * Meeting planned with Linux IT to answer questions about potential scope we had
+    shared/other questions.
+
+## Upcoming Meetings
+
+* **Node.js Foundation Calendar**: https://nodejs.org/calendar
+
+Click `+GoogleCalendar` at the bottom right to add to your own Google calendar.