Node.js Foundation Technical Steering Committee (TSC) Meeting 2019-01-23 #655
Comments
|
I can chair this if it's needed. |
|
No agenda items, so seems like a high likelihood of cancelling. Two things it is worth looking over and preparing for in general are nodejs/node#22584 and nodejs/node#21351. One or both will almost certainly will come before TSC before the April release. They are controversial things with long histories. It would be great if, when the inevitable discussion occurs, everyone who is participating sounds prepared. I will likely miss the first 15+ minutes, but can attend otherwise. |
|
There is a security issue we should talk about. |
|
I'll be there and can Chair. There is other business as well that we should discuss so would like to hold the meeting. |
|
There should be issues on the agenda, for some reason the tool failed to generate them properly. Investigating. |
|
Ok have added the missing issues. |
|
For the NODE_MODULE_VERSION ABI issue (#651), perhaps invite @codebytere to attend as a guest? Maybe after confirming that there will be sufficient attendance by invested/informed folks? Maybe folks can self-nominate on that front, but judging from the issues and previous conversations, likely candidates might be @gabrielschulhof @mhdawson @mcollina @MylesBorins @ofrobots @rvagg |
|
@gabrielschulhof @mhdawson @mcollina @MylesBorins @ofrobots @rvagg can you chime in if you can make it. If enough can we can see if @codebytere can make it. |
|
Won't be making it, 3am, but for the But we need to keep track of these reservations; hence my proposal for a registry @ nodejs/node#24114 - one central place to keep a record, machine readable and easy to PR a request to reserve for Electron and others that need a number. Incrementing is cheap, there shouldn't be a reason to block anyone requesting as long as we can do it in a coordinated fashion. I haven't forgotten about that PR, it's just been a low priority and there was a good suggestion for more metadata that I was considering changing the format to incorporate. |
|
I don't think nodejs/node#20803 should be on the agenda. It looks like the request was for TSC to review the PR since it's semver-major. I do not think there is anything to discuss at the meeting... |
|
@apapirovski I agree that it's not really sonething to discuss. I only added it because no one pointed it in any direction and that seems pretty bad. It would be good to get any response. Yes, there were a few comments but no one either gave a LG or said anything against landing it. For that reason I kindly ask the TSC members to review more semver-major PRs as it's otherwise difficult to deal with these. |
|
I can't make it on this timeslot unfortunately.
…On Wed, Jan 23, 2019, 7:42 AM Anatoli Papirovski ***@***.*** wrote:
I don't think nodejs/node#20803
<nodejs/node#20803> should be on the agenda. It
looks like the request was for TSC to review the PR since it's
semver-major. I do not think there is anything to discuss at the meeting...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#655 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAE0qXegqWX_OxXx5AviqsONYIgrUuoTks5vGILHgaJpZM4aKyRI>
.
|
|
Sorry for the delay. No significant moderation team activities this week. cc @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
|
Minutes PR is #658 so I think this can be closed. |
Time
UTC Wed 23-Jan-2019 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
nodejs/TSC
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: