Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-04-04 #516
Comments
Once again, it would be cool if I could remind people that nodejs/node#19524 could really use some TSC review, otherwise it might just not happen (not an outcome I would mind, but this general approach is what we decided on, I think…) |
|
I'd like to add a small agenda item to discuss if we can unblock Zones which was blocked a long while ago due to signals from Node before we had as good documentation on process / decisions. Just want to give a small 10minute presentation and see if blocking it based upon having Error handling is still true since Promises are becoming more used and have similar concerns. CC: @trevnorris |
I don't know the history, but given the last comment in that thread, revisiting seems reasonable: |
|
I think a short presentation would be nice. It’s important to note that the diagnostics wg is looking at modeling the async context as well, and I see providing a context local storage implementation a need for the platform. The concerns about error handling and performance remains. |
|
The nomination of @mafintosh was announced during the meeting on 2018-03-28 (#513) and he will be onboarded by @jasnell as per update in nodejs/node/issues/19148 |
You are no doubt correct that it does not need to be on the agenda. However, for very good reasons, no one is permitted to remove an agenda item except the person who added it in the first place. So @mcollina has to remove it. Otherwise, we'll have to spend 7 seconds on it during the meeting. (Might not be the worst use of time to celebrate an onboarding.) |
|
@Trott done! |
|
Adding nodejs/node#19524. I anticipate a call for a vote and a need to act quickly, so please review that PR if you have not done so already. |
|
Adding nodejs/node#18138 to the agenda. It needs a second TSC reviewer besides @jasnell. Adding it to the agenda solely to identify someone who can review it soon-ish. If a TSC member reviews it between now and the meeting, it can be removed from the agenda. |
|
Adding nodejs/node#18994 for the same reason. |
|
@bmeck are you ready to have it on today's agenda or should we plan for next week? |
|
Sorry, can't make it today. Last minute scheduling conflict |
|
@bmeck at this point maybe next week makes the most sense. What do you think? |
|
Moderation Team update: No actions taken this week. @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
|
PR for minutes #517, probably needs some fix up as its a quick cut/paste. |
Time
UTC Wed 04-Apr-2018 17:00 (05: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
node_modules#19524nodejs/TSC
nodejs/modules
Invited
Observers
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
https://zoom.us/j/441168935
Same password as usual
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
The text was updated successfully, but these errors were encountered: