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 2016-01-14 #31

Closed
rvagg opened this issue Jan 14, 2016 · 3 comments
Closed

Comments

@rvagg
Copy link
Member

rvagg commented Jan 14, 2016

Time

UTC Thu 14-Jan-2016 20:00:

  • San Francisco: Thu 14-Jan-2016 12:00
  • New York: Thu 14-Jan-2016 15:00
  • Amsterdam: Thu 14-Jan-2016 21:00
  • Moscow: Thu 14-Jan-2016 23:00
  • Sydney: Fri 15-Jan-2016 07:00
  • Tokyo: Fri 15-Jan-2016 05:00

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

  • invite prior contributors to the nodejs org #3802

nodejs/TSC

  • add inclusivity working group #29

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.

@rvagg
Copy link
Member Author

rvagg commented Jan 14, 2016

I'd like us to quickly chat about what we're going to do with membership so we can get proper quorums at these things. Do we need make some moves on encouraging folks who don't want this particular style of bikeshed to resign from the TSC? Then we should also talk about the expansion process. We have some areas of the org already that we could consider inviting people in from and I think if we accept #29 we need to ask Inclusivity to nominate someone too.

@rvagg
Copy link
Member Author

rvagg commented Jan 14, 2016

You should all have a calendar invite for this, I've set it to UTC 20:00 and done the same for the CTC one. I think the previous CTC (old TSC) one was set to my timezone which was not so optimal.

@williamkapke
Copy link
Contributor

Minutes added in #111

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

No branches or pull requests

2 participants