Node.js Technical Steering Committee (TSC) Meeting 2023-01-04 #1323
Comments
|
I won't be able to join this meeting. |
|
nodejs/node#45900 should be on the agenda. Perhaps the script isn't checking discussions? |
|
@GeoffreyBooth discussions did not exist when the script was written, so it is possible. |
|
@mcollina we've been waiting for you to lead the discussion on: doc: change fetch from experimental to stable nodejs/node#45684 unless you tell us otherwise, we'll likely defer these 3 again until next time when you are available. |
I think we can decide on that now? So our agenda could become:
The |
|
Given how the meeting rotates, I'll join on the 18th. |
|
I'm -1 to the approach in nodejs/node#45900. I agree some clarification is needed, but I think we have a good pace of shipping new features right now and adding more process is going to stall the project. |
Could you add a comment on that discussion please? With your specific objections or what alternatives you think are better. I’d like to avoid this being an up or down vote on a proposal, or a situation where I need to defend a proposal from lots of people lodging objections to it. There are real problems that prompted me to write this proposal, and I’d like the TSC as a group to discuss what the best solutions are. Maybe we collectively decide that none of the solutions are better than the status quo, and that’s fine, but I want us to all engage constructively into making that decision. I don’t want the burden to be on me to function like a legislator where I need to propose a bill text and whip votes; let’s work together to figure out the best way to revise our processes, if that’s what we decide that we need to do. |
|
It's probably too late, but could we maybe add discussing npm/rfcs#665 to the agenda? I've been recommended to reach out to the TSC about this. |
This is the Node.js TSC, we have no overview over what the npm team implements and no saying on RFCs for npm. TSC members can of course give their opinion on the matter, but it is outside of the scope of the TSC as a group. |
I think the correct issue would be nodejs/node#46074. Whether or not this should be handled in the NPM scope, can be an outcome of the TSC meeting. |
The TSC would typically defer to the issue tracker to see if a consensus emerges in the community. On top of that, TSC saying it's in the Node.js scope would have little value if no one is doing the actual work on implementing the feature, so until there's an implementation candidate discussing it in TSC meeting would not be a good use of everyone time IMO. That being said, anyone can add the issue to the TSC agenda for awareness, so TSC members can chime in the issue if they have something to add to the discussion (tagging the TSC would more or less have the same effect, except that GitHub notifications are easier to miss than an item on the agenda). |
|
PR for minutes - #1324 |
Time
UTC Wed 04-Jan-2023 16:00 (04: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
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.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: