-
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-07-25 #573
Comments
I'm not going to be able to make it this week as I'm at Node Summit and I believe there are a number of other people who are here as well. In addition, people from Google have a conference going on as well. I suggest we cancel for this week unless somebody volunteers to chair and confirms there are enough TSC member available. |
I'm +1 for canceling. |
I'm at NodeSummit too but happy to have the meeting and run it if there's enough interest. |
Also not going to make it. |
If we go ahead perhaps those of us at NodeSummit who can spare the time should find a space to attend the meeting together in person. |
I have talks to deliver and would have to be in the speaker prep during the meeting so I can't make it in that time. @Trott thanks for volunteering. I'll leave it up to you to figure out if there are enough people who can attend and to chair the meeting. |
I can attend but would prefer not to (midnight in my timezone). |
Same as @targos — 1 AM in my zone, I can attend but would prefer not to. |
Given the absence of enthusiasm, let's cancel, yeah? I'll be around and online if anyone wants to have a micro-subcommittee meeting about anything. :-D |
Moderation team report for the last week: Removed useless comment from apparent bot user. Moderation issue 221. Removed useless non-Collaborator comment possibly left in error. Moderation issue 222. @nodejs/tsc @nodejs/community-committee @nodejs/moderation |
One thing I would include in the announcements segment if the meeting were to occur would be the nomination of @rubys as a Collaborator. I'll arrange onboarding soon (possibly very soon). |
Possibly I'm misinterpreting this, but isn't onboarding done usually after the nomination is accepted, which according to our GOVERNANCE is one week after the issue (nodejs/node#21974) is opened? Just to be clear I'm querying the process -- I'm 💯 behind the nomination. |
I'm not going to be around for it. |
@richardlau Yes, you are correct. Which is a shame from my perspective because I just scheduled the onboarding for Monday. |
It’s more 5 minutes into the meeting time and there’s nothing happening on zoom, so I think it’s okay to close this. 🙂 |
Time
UTC Wed 25-Jul-2018 22:00 (10: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/build
nodejs/node
nodejs/docker-node
nodejs/TSC
nodejs/user-feedback
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
The text was updated successfully, but these errors were encountered: