-
Notifications
You must be signed in to change notification settings - Fork 133
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 2019-01-16 #653
Comments
Unfortunately i won't be able to chair this one, as I'm traveling in India and I will be at a client at that given time. |
@nodejs/tsc, any other volunteers to chair this week. Due to the time as usual I can't make it either. |
I can't ever make that timeslot unfortunately, otherwise I would. |
@nodejs/tsc I can't make that time and its pretty late today. We also only have 1 person saying they can make the meeting. I'm going to leave the issue open in case somebody volunteers and can run the meeting, but at this point it's not looking too good. At this point I'd suggest we consider #650 the Vote from bringing @Trott back onto the TSC. Seems like we have 13/17 who have voted yes and no objections so unless there are objections before the planned time for this meeting (or in the meeting) I think the vote will have been completed in favor. |
@mhdawson I haven't chaired before but if I can get some pointers about how to set things up (like the streaming) I'm willing chair. |
@danbev are you available at 5EST for a walkthrough. We'd also have to give you access to the youtube account and zoom account but as a TSC member I don't think that is an issue. |
I was not able to catch up with @danbev today so was not able to do any handover. Of those who have said they "might" be able to make the meeting I think @MylesBorins and @cjihrig ,would be able to start the meeting and stream and then @danbev could chair. Either way @danbev lets plan to get together so that I can walk you through so that you'd be able to chair/start stream etc. in the future. |
My "might" is most likely a "no." 7am usually doesn't work for me. |
I can join to kick off the stream and start youtube. I won’t be able to stay for the full meeting. |
No significant moderation team activities this week. cc @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
PR for minutes: #654 |
Time
UTC Wed 16-Jan-2019 12:00 (12: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-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
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: