Repository navigation
Node.js Technical Steering Committee (TSC) Meeting 2020-08-13 #907
Description
Time
UTC Thu 13-Aug-2020 21:00 (09:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Thu 13-Aug-2020 14:00 (02:00 PM) |
| US / Mountain | Thu 13-Aug-2020 15:00 (03:00 PM) |
| US / Central | Thu 13-Aug-2020 16:00 (04:00 PM) |
| US / Eastern | Thu 13-Aug-2020 17:00 (05:00 PM) |
| London | Thu 13-Aug-2020 22:00 (10:00 PM) |
| Amsterdam | Thu 13-Aug-2020 23:00 (11:00 PM) |
| Moscow | Fri 14-Aug-2020 00:00 (12:00 AM) |
| Chennai | Fri 14-Aug-2020 02:30 (02:30 AM) |
| Hangzhou | Fri 14-Aug-2020 05:00 (05:00 AM) |
| Tokyo | Fri 14-Aug-2020 06:00 (06:00 AM) |
| Sydney | Fri 14-Aug-2020 07:00 (07:00 AM) |
Or in your local time:
- http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2020-08-13&iso=20200813T21
- or http://www.wolframalpha.com/input/?i=09PM+UTC%2C+Aug+13%2C+2020+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1gd3udsqp-fNeXRQRI2JrPAu41no4R-sNAZOByuRi0Ow/edit
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- Land #34035 on v14 (stream: simpler Readable async iterator) #34680
- Rename default branch from "master" to "main" or something similar #33864
nodejs/admin
- Audit Google account access #389
Invited
- Anna Henningsen @addaleax (TSC)
- Anatoli Papirovski @apapirovski (TSC)
- Beth Griggs @BethGriggs (TSC)
- Ruben Bridgewater @BridgeAR (TSC)
- Сковорода Никита Андреевич @ChALkeR (TSC)
- Colin Ihrig @cjihrig (TSC)
- Shelley Vohr @codebytere (TSC)
- Daniel Bevenius @danbev (TSC)
- Franziska Hinkelmann @fhinkel (TSC)
- Gabriel Schulhof @gabrielschulhof (TSC)
- Gireesh Punathil @gireeshpunathil (TSC)
- James Snell @jasnell (TSC)
- Joyee Cheung @joyeecheung (TSC)
- Mary Marchini @mmarchini (TSC)
- Matteo Collina @mcollina (TSC)
- Michael Dawson @mhdawson (TSC)
- Myles Borins @MylesBorins (TSC)
- Michaël Zasso @targos (TSC)
- Tobias Nießen @tniessen (TSC)
- Rich Trott @Trott (TSC)
Observers/Guests
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
Zoom link: https://zoom.us/j/611357642
Regular password
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.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
- 👍 - Attending
- 👎 - Not attending
- 😕 - Not sure yet
Activity
mmarchini commentedon Aug 10, 2020
The unhandled rejections survey is available at: https://www.surveymonkey.com/r/FTJM7YD
We also wrote an accompanying blog post for extra context: https://medium.com/@nodejs/node-js-promise-reject-use-case-survey-98e3328340c9
The survey will run for at least two weeks, at which point we'll evaluate if the number of replies is enough for us to move forward, otherwise we might extend it for a week or two. Please fill out the survey as it will help us decide the future of unhandled promise rejections on Node.js!
mmarchini commentedon Aug 11, 2020
The Commit Queue PR is ready to land. I was going to land it today but @devsnek pointed out that it will allow non-collaborators to
start CI (more specifically, it will allow the new Triage team to start CI as well)land pull requests (if the pull request passes all checks, including wait time, number of reviews by collaborators, and CI). I don't think we have a process to give an extra teamaccess to CIpartial landing permissions to nodejs/node, so I'll just leave the question here: should the Triage team be able tostart CIland pull requests using the Commit Queue on nodejs/node?If someone objects we can discuss in the meeting, but so far folks were fine with it in the PR.
Ref: nodejs/node#34112
mhdawson commentedon Aug 11, 2020
I think having them start CI is ok, and possibly desirable.
mhdawson commentedon Aug 11, 2020
@ronag is going to come to the meeting for the discussion on Land #34035 on v14 (stream: simpler Readable async iterator) #34680
mmarchini commentedon Aug 11, 2020
I made a mistake on my comment above: Triage team will be able to start Commit Queue, not CI (they already can start CI today :) ). So let me rephrase my question: should the triage team be allowed to start Commit Queue, which means they will be able to land pull requests? As @addaleax mentioned in the PR, triage team will still not count towards reviews, and the Commit Queue runs all the necessary checks before landing (wait time, reviews, CI, etc). This might help offload some landing work from collaborators, which is good. OTOH it gives partial commit permission to a team separate from collaborators. So what do folks think?
Trott commentedon Aug 12, 2020
Moderation Team report:
Blocked 2 users for junk/spam PRs: https://github.com/nodejs/moderation/issues/373, https://github.com/nodejs/moderation/issues/372
@nodejs/moderation @nodejs/community-committee @nodejs/tsc
mcollina commentedon Aug 12, 2020
I'm +1 @mmarchini
mhdawson commentedon Aug 13, 2020
No update on the build resources strategic initiative.
mhdawson commentedon Aug 13, 2020
I'm +1 @mmarchini as well.
MylesBorins commentedon Aug 13, 2020
@mmarchini I think it is a great idea! We may want to document and encourage usage of the "author ready" label or some other mechanism to signal "this can land'.
edit: or alternatively encourage / normalize the use of changes requested to ensure there are not misunderstandings (my understanding is work on this is already being done)
mmarchini commentedon Aug 13, 2020
We changed the collaborator guide recently to explicitly require Request Changes when objecting to a PR (nodejs/node#34639 and nodejs/node#34702). Might be worth a PSA?
mmarchini commentedon Aug 13, 2020
Posted a PSA on https://github.com/orgs/nodejs/teams/collaborators/discussions/106
mhdawson commentedon Aug 13, 2020
PR for minutes: #909