-
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 2018-05-30 #547
Comments
Considering that a good chunk of us will be in Berlin, should we postpone or do it in person? |
+1 to in person meeting during summit if possible
Might be fun to do with a “live studio audience"
… On May 28, 2018, at 2:23 PM, Matteo Collina ***@***.***> wrote:
Considering that a good chunk of us will be in Berlin, should we postpone or do it in person?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#547 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV9t-4kudkR8FcK8qkhFr3uQcGehdks5t2-xXgaJpZM4UQGCH>.
|
+1 to a summit meeting |
If you meet in person, please still have a remote dial in for those of us who will not be there |
For me it would come down to whether people can make the regular time or not. We'll have lots of things to talk about at the summit and I don't think need we need to consume an hour on topics people may or may not be interested in. |
I most likely will be travelling to Berlin during the regular meeting time. |
I should be on a plane during the meeting time. |
I can make the regular time and chair the meeting. But I'm fine with cancelling if too many folks are traveling. |
I will already be in Berlin at the regular time. I can try to make it. |
I should be able to make it as well, but also ok with cancelling if too many people can't make it. |
I'll be in Berlin and can make the meeting time. Some of these items seem like they should be resolve-able without a meeting: |
Let's cancel this because so many people are traveling. @nodejs/tsc could you please weigh in on nodejs/node#20725. Please reopen if I made the decision to cancel prematurely. |
Moderation Team update: No moderation actions taken this week. @nodejs/moderation @nodejs/tsc @nodejs/community-committee |
Time
UTC Wed 30-May-2018 14:00 (02: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
nodejs/i18n
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
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
The text was updated successfully, but these errors were encountered: