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 Core Technical Committee (CTC) Meeting 2016-05-25 #6968

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

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-05-25 #6968

rvagg opened this issue May 25, 2016 · 11 comments

Comments

@rvagg
Copy link
Member

rvagg commented May 25, 2016

Time

UTC Wed 25-May-2016 20:00:

  • San Francisco: Wed 25-May-2016 13:00
  • New York: Wed 25-May-2016 16:00
  • Amsterdam: Wed 25-May-2016 22:00
  • Moscow: Wed 25-May-2016 23:00
  • Sydney: Thu 26-May-2016 06:00
  • Tokyo: Thu 26-May-2016 05:00

Or in your local time:

Links

Agenda

Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

  • Add v8_inspector support #6792
  • process: flush stdout/stderr upon process.exit() #6773

Invited

Notes

The agenda comes from issues labelled with ctc-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 CTC 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 May 25, 2016

Note that the CTC agreed to add Bradley Meck in observer status to its meeting invites due to the his long history and technical depth with Node.js and also his new connection to TC39 via the GoDaddy seat where he will be a representative of Node.js' interests there.

His efforts in driving the discussions around ES Modules have been invaluable to Node and, having worked with Bradley before, I'm confident he'll apply himself to these spec-type discussions with the kind of rigour that I think will be difficult to match across our team.

@ofrobots
Copy link
Contributor

For the discussion on #6792 I would like invite @pavelfeldman (DevTools tech lead) to the meeting, if there are no objections.

@bnoordhuis
Copy link
Member

@ofrobots Good idea.

@shigeki
Copy link
Contributor

shigeki commented May 25, 2016

I regret my absence today, sorry.

@Trott
Copy link
Member

Trott commented May 25, 2016

Updated Michael Dawson in the attendance list to say (CTC).

@Trott
Copy link
Member

Trott commented May 25, 2016

The StandUp section of the Google doc is all set for people who want to get an early jump on filling theirs out.

@bmeck
Copy link
Member

bmeck commented May 25, 2016

I will be missing today. Not much to report, just getting in touch with APM vendors about how ES modules would affect them.

@ChALkeR
Copy link
Member

ChALkeR commented May 25, 2016

Sorry, I will miss today's meeting.

@Fishrock123
Copy link
Contributor

Fishrock123 commented May 25, 2016

Livestream viewers, max 7.

node_livestream_viewers-2015-05-25

@bmeck
Copy link
Member

bmeck commented May 25, 2016

need to update youtube links in future to have the /c/

@Trott
Copy link
Member

Trott commented May 25, 2016

need to update youtube links in future to have the /c/

Just in case it's a copy/paste every time, I'm going to go and edit it above right now...

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

10 participants