-
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-11-29 #429
Comments
I probably won't make it this week. |
Observers this week should include @danbev and @williamkapke. I'm going to have a hard time making this one but I'll try. |
I'll do my best to make it but it will be quite late for me in Tokyo
…On Nov 28, 2017 9:35 PM, "Rich Trott" ***@***.***> wrote:
Observers this week should include @danbev <https://github.com/danbev>
and @williamkapke <https://github.com/williamkapke>.
I'm going to have a hard time making this one but I'll try.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#429 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV2rD5MRn5Q05FgzjzfjW-Fri_uqIks5s6_31gaJpZM4Qrrxf>
.
|
@Trott I'd be happy if you just added the observers to the issue as opposed to in a comment. |
@jasnell you added #16170, do you agree we should remove ? |
I think if I do that, they don't get notified. But I'm happy to do that in addition to commenting! :-D |
(Also: @mhdawson I corrected Michaël Zasso's name here and in the Google doc. It was showing up as MichëZasso, so you've got the umlaut showing up now, but missing a couple characters after it....) |
@Trott thanks, it comes from here: https://github.com/mhdawson/create-node-meeting-artifacts/blob/master/templates/invited_TSC. I can never tell if missing characters are because of the overwrite that often happens with the special characters or something is missing. I'll see if I can add that single character. |
@Trott updating an commenting +1 |
BTW I don't mind if you omit the accent in my name, if that can help. |
No update on #371 |
I'm probably going to miss this one I'm afraid |
Thanks for the invite. I’m onsite at MasterCard this week & I’m on network lockdown. Sry to miss- I’ll catch the YouTube video later. |
PR for minutes: #430 |
Time
UTC Wed 29-Nov-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
.m.js
intent for ESM #16170nodejs/TSC
Other
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: