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-05-05 #99

Closed
rvagg opened this issue May 5, 2016 · 11 comments
Closed

Comments

@rvagg
Copy link
Member

rvagg commented May 5, 2016

Time

UTC Thu 05-May-2016 20:00:

  • San Francisco: Thu 05-May-2016 13:00
  • New York: Thu 05-May-2016 16:00
  • Amsterdam: Thu 05-May-2016 22:00
  • Moscow: Thu 05-May-2016 23:00
  • Sydney: Fri 06-May-2016 06:00
  • Tokyo: Fri 06-May-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/build

  • OS X buildbots/ci: call to action #367

nodejs/TSC

  • Define "Node.js core" #84

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.

Public participation

We will attempt to stream our Uberconference call straight to YouTube so anyone can listen to it live. If it works, then it should start playing at https://www.youtube.com/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 will also be watching the YouTube feed for quesitons posted there, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular.

@jasnell
Copy link
Member

jasnell commented May 5, 2016

My regrets. I will not be able to join today's discussion.

@joshgav
Copy link
Contributor

joshgav commented May 5, 2016

I'm planning to listen on YouTube.

@mikeal
Copy link
Contributor

mikeal commented May 5, 2016

Are we using Google Hangouts On Air?

@Fishrock123
Copy link
Contributor

@mikeal it says uberconference

@mikeal
Copy link
Contributor

mikeal commented May 5, 2016

That isn't working right now, we're still trying to transfer the accounts over to the LF.

@Fishrock123
Copy link
Contributor

@mikeal it's on Rod's account

@mikeal
Copy link
Contributor

mikeal commented May 5, 2016

I can setup a GoToMeeting or a Google Hangout on Air if need be.

@jasnell
Copy link
Member

jasnell commented May 5, 2016

Rod set up a different account for use in the interim. We used it yesterday
for the CTC call.
On May 5, 2016 1:01 PM, "Mikeal Rogers" [email protected] wrote:

That isn't working right now, we're still trying to transfer the accounts
over to the LF.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#99 (comment)

@mikeal
Copy link
Contributor

mikeal commented May 5, 2016

Can someone send me the dialin?

@rvagg
Copy link
Member Author

rvagg commented May 5, 2016

see google doc

@Fishrock123
Copy link
Contributor

Livestream viewers, max 6.

node_livestream_viewers-2016-05-05

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

5 participants