Node.js Technical Steering Committee (TSC) Meeting 2020-08-13 #907
Comments
|
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! |
|
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 If someone objects we can discuss in the meeting, but so far folks were fine with it in the PR. Ref: nodejs/node#34112 |
|
I think having them start CI is ok, and possibly desirable. |
|
@ronag is going to come to the meeting for the discussion on Land #34035 on v14 (stream: simpler Readable async iterator) #34680 |
|
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? |
|
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 |
|
I'm +1 @mmarchini |
|
No update on the build resources strategic initiative. |
|
I'm +1 @mmarchini as well. |
|
@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) |
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? |
|
PR for minutes: #909 |
Time
UTC Thu 13-Aug-2020 21:00 (09:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/admin
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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.
The text was updated successfully, but these errors were encountered: