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.

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-01-26 #196

Closed
rvagg opened this issue Jan 26, 2017 · 8 comments
Closed

Comments

@rvagg
Copy link
Member

rvagg commented Jan 26, 2017

Time

UTC Thu 26-Jan-2017 20:00 (08:00 pm):

Timezone Date/Time
US / Pacific Thu 26-Jan-2017 12:00 (12:00 pm)
US / Mountain Thu 26-Jan-2017 13:00 (01:00 pm)
US / Central Thu 26-Jan-2017 14:00 (02:00 pm)
US / Eastern Thu 26-Jan-2017 15:00 (03:00 pm)
Amsterdam Thu 26-Jan-2017 21:00 (09:00 pm)
Moscow Thu 26-Jan-2017 23:00 (11:00 pm)
Chennai Fri 27-Jan-2017 01:30 (01:30 am)
Tokyo Fri 27-Jan-2017 05:00 (05:00 am)
Sydney Fri 27-Jan-2017 07:00 (07:00 am)

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

  • Copyright Date #195
  • General update to the Member Travel Fund doc #181
  • Formation of a Security Working Group #175
  • Updating the Copyright #174
  • charter: revised membership rules #142
  • Investigate moving nvm into the foundation #96

Invited

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.

A standing invitation exists for all @nodejs/CTC members who are not also TSC members to attend in observer capacity.

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 it.

@rvagg
Copy link
Member Author

rvagg commented Jan 26, 2017

NOTE I won't be able to make this meeting, I'm finally moving house and will be busy with removalists while this meeting is running. Things should start to settle down for me after this hectic January when I get settled in to my new office.

@nebrius || @williamkapke would either of you like to run the meeting? Also up to you to make a call as to whether to have a meeting or not—I'm not sure there's much new stuff to cover except maybe getting some updates on security WG and version management.

@joshgav
Copy link
Contributor

joshgav commented Jan 26, 2017

Should we try to move #142 forward? I think it's the last step to clarifying TSC procedures. /cc @jasnell

Let me try to get an update on the version management investigation this morning.

@joshgav
Copy link
Contributor

joshgav commented Jan 26, 2017

Also, can we get an update on what's happening with the Security WG per #175? /cc @sam-github

@joshgav
Copy link
Contributor

joshgav commented Jan 26, 2017

One more 😉 : @hackygolucky (or @nebrius?) want to give an update on #179 and the Community Committee?

I put all of these in the agenda in the Google Doc too.

@bnoordhuis
Copy link
Member

I don't think I'll be able to make it tonight for a change. I've opened #198 to discuss rotating the meeting times.

@nebrius
Copy link
Contributor

nebrius commented Jan 26, 2017

Unfortunately I fell ill this morning, and I'm going to need to skip this meeting too. @williamkapke, can you run the meeting?

@nebrius
Copy link
Contributor

nebrius commented Jan 26, 2017

Also, I'm a +1 on rotating meeting times, fwiw

@joshgav
Copy link
Contributor

joshgav commented Jan 26, 2017

notes in #199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants