-
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-03-09 #222
Labels
Comments
I can't make it. My vote is +1 to both issues. |
I can't make it; +1 on Josh |
I'll be joining from outside the office, if someone else could handle notes. Thanks! |
PR for minutes, #223 just need to add the audio recording |
Minutes landed, closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Time
UTC Thu 09-Mar-2017 20:00 (08: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/summit
nodejs/TSC
nodejs/community-committee
Invited
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 shouldbe on the agenda before the meeting starts.
Joining the meeting
Uberconference; participants should have the link & numbers, contact me if you don't.
A standing invitation exists for all @nodejs/CTC members who are not also TSC members to attend in observer capacity.
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 agen
da item, this is a good place for it.
The text was updated successfully, but these errors were encountered: