-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-12-20 #447
Comments
@fhinkel We agreed at the last meeting @jasnell attended that we would keep that labeled Related: I'm removing that item from this agenda and from the Google doc. That said, if we think it needs discussing this week, please add it back or (perhaps slightly better) open a separate issue which more precisely frames the issue that needs discussion sooner rather than later. |
Observers to invite: @gibfahn and @BridgeAR for nodejs/node#14795 At the meeting, I will probably propose that we table #443 because @mhdawson is on vacation this week and next. @MylesBorins Do we need to keep #311 on the agenda? (Not advocating, just asking.) |
nodejs/build
nodejs/node
nodejs/TSC
|
Looks like @danbev hasn't been added to the invite list yet, so @-mentioning them here for notification purposes. |
(Also, just added @danbev manually to the original post here and the minutes doc.) |
Thanks, I actually thought that this was because I marked that time in the spreadsheet as a bad time for me. l might not make it I'm afraid (still trying to see if I might get a sitter and will know for sure tomorrow). |
Sorry, I won't be able to make it today. |
I won’t be able to make it either |
4am for me, opting out |
Eating lunch with my little girl for her birthday, so I won't be able to make it today. I should be back next week though. |
Thanks for inviting me but I probably can not make it as I am going to be at the airport at that time. I guess @gibfahn is the best person to talk to in this case anyway. |
I'll be able to make and stream it |
Thanks, @rvagg. I need to start using https://github.com/nodejs/node-meeting-agenda, with |
Minutes: #451 |
Had a fever last night and was not able to make it, sorry. |
Time
UTC Wed 20-Dec-2017 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
nodejs/TSC
Invited
Observers
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
Uberconference; participants should have the link & numbers, contact me if you don't.
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: