Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-01-03 #458

Closed
mhdawson opened this issue Jan 1, 2018 · 17 comments
Closed

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-01-03 #458

mhdawson opened this issue Jan 1, 2018 · 17 comments
Assignees
@mhdawson
Labels
tsc-meeting

Comments

@mhdawson
Copy link
Member

mhdawson commented Jan 1, 2018 •
edited by Trott
Loading

Time

UTC Wed 03-Jan-2018 12:00 (12:00 PM):

Timezone Date/Time
US / Pacific Wed 03-Jan-2018 04:00 (04:00 AM)
US / Mountain Wed 03-Jan-2018 05:00 (05:00 AM)
US / Central Wed 03-Jan-2018 06:00 (06:00 AM)
US / Eastern Wed 03-Jan-2018 07:00 (07:00 AM)
London Wed 03-Jan-2018 12:00 (12:00 PM)
Amsterdam Wed 03-Jan-2018 13:00 (01:00 PM)
Moscow Wed 03-Jan-2018 15:00 (03:00 PM)
Chennai Wed 03-Jan-2018 17:30 (05:30 PM)
Hangzhou Wed 03-Jan-2018 20:00 (08:00 PM)
Tokyo Wed 03-Jan-2018 21:00 (09:00 PM)
Sydney Wed 03-Jan-2018 23:00 (11: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/TSC

  • Mentorship initiative ramping up. #443
  • Enterprise Advisory Group #431
  • Strategic Initiatives - Tracking Issue #423
  • Document guidelines for accountability expectations for all members of the TSC and CommComm #311

nodejs/admin

  • GitHub Owner permissions #33

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
@mhdawson mhdawson self-assigned this Jan 1, 2018
@danbev
Copy link
Contributor

danbev commented Jan 1, 2018 via email

@addaleax
Copy link
Member

addaleax commented Jan 1, 2018

I’ll have to miss this one too, sorry.

@mcollina
Copy link
Member

mcollina commented Jan 1, 2018

I thought we agreed to skip this one too, but I will be online. I can potentially stream or chair if needed.

@MylesBorins
Copy link
Contributor

MylesBorins commented Jan 1, 2018 via email

@jasnell
Copy link
Member

jasnell commented Jan 1, 2018

I'd prefer to skip this week.

@cjihrig
Copy link
Contributor

cjihrig commented Jan 1, 2018

I'll likely miss this one.

@Trott
Copy link
Member

Trott commented Jan 2, 2018

I can (probably) make this one. I think @joyeecheung was planning to chair, but I could be wrong.

Whether or not we cancel, it would be really helpful to get more TSC approvals and/or feedback on #456.

@Trott
Copy link
Member

Trott commented Jan 2, 2018

(I added @danbev to the post and the GitHub doc. @mhdawson if you could add him to your automated job at your earliest convenience, that would be great!)

@Trott
Copy link
Member

Trott commented Jan 2, 2018

Might be a good idea for more people to look at nodejs/node#17581 too. It's a pretty significant change to assert.

@joyeecheung
Copy link
Member

joyeecheung commented Jan 2, 2018 •
edited
Loading

@Trott I prefer not to chair meetings while I am in China due to network reliability issues (doesn't happen often, but GFW is unpredictable. When it beats my proxy I won't be able to access either Youtube or Google docs i.e. any Google services and the Uberconf connection could get lost). It will be better if you or @mcollina chair this one if we do not skip it, sorry.

@targos
Copy link
Member

targos commented Jan 2, 2018

Sorry for the late reply. I can't make it this time.

@fhinkel
Copy link
Member

fhinkel commented Jan 2, 2018

I checked the issues: They're all waiting for input from folks who can't make it tomorrow. I'm in favor of skipping.

@mhdawson
Copy link
Member Author

mhdawson commented Jan 2, 2018

Just back from holiday and catching up but this meeting it too early for me so I won't make it.

On #443 I just added to the agenda to make sure the TSC was aware and those interested in mentoring/defining the process chimed in as part of the discussion. It was my action from the CommComm meeting where it was presented. If there was enough interest we could ask for a repeat of the presentation as well.

@Trott
Copy link
Member

Trott commented Jan 3, 2018

I think we should officially cancel at this time, since no one seems to have a particular sense of urgency that the meeting must or even should happen this week.

@mhdawson I know it's getting late in your time zone, but perhaps you can officially provide the "it's canceled" comment here as the TSC Chair? I don't think we want to wait much longer as canceling with too much less than 12 hours notice seems like something we should endeavor to avoid as much as we can...

@evanlucas
Copy link
Contributor

+1 to skipping

@rvagg
Copy link
Member

rvagg commented Jan 3, 2018

nobody else is on the call at 6 minutes past so it's officially cancelled!

@rvagg rvagg closed this as completed Jan 3, 2018
@mhdawson
Copy link
Member Author

mhdawson commented Jan 3, 2018

@Trott, sorry but I was already gone for the day so I missed your suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhdawson mhdawson

Labels
tsc-meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests