-
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-04-25 #529
Comments
Argh, good chance I can't make this meeting. We'll see. In any event... @MylesBorins Should #476 be removed from this week's meeting? Or is there something to talk about there? |
I’m on vacation and I won’t be able to attend. |
@Trott we have a board meeting next Monday, so it would be nice to leave it on the agenda in case anyone has anything they want me to bring to the board |
@MylesBorins OK, sounds good, although I'd like to publicly encourage anyone who has such an item to leave it here or open an issue rather than waiting for the meeting to bring it up. I'd also like to discourage people from trying to think up things at the actual meeting. |
I'll have to skip this meeting as well, due to scheduling conflict. Also, is there a place where I can file an issue to update my current status as a TSC member rather than an observer in the meeting template? I fixed this one manually. |
@MylesBorins WHATWG participation issue looks like a good fit. #532 I have added it to the agenda. |
@TimothyGu you can file a PR here: https://github.com/mhdawson/create-node-meeting-artifacts/tree/master/templates. Just update the invited and observer files for the TSC. If you can do that I'll make sure to land before the next meeting is generated. Otherwise I'll try to get to it myself. |
I'll be running late due to a scheduling conflict. |
I can't make it today. I'll post a moderation team update here later. And I'll finish up the concise Buffer deprecation doc and post it to Medium this week, crediting everyone who commented on the draft distributed to TSC. If you don't want to be acknowledged, let me know. |
Sorry, I will most likely have to miss the meeting today — onetime time conflict. |
Going to be late. Need to password if someone can send it to me. |
Moderation Team Update for the last week: One user was blocked for spamming. Their account was eventually removed from GitHub. Moderation repo issue 196. No other significant Moderation Team activity. @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
Time
UTC Wed 25-Apr-2018 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
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: