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-06-15 #7307

Closed
rvagg opened this issue Jun 15, 2016 · 9 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-06-15 #7307

rvagg opened this issue Jun 15, 2016 · 9 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@rvagg
Copy link
Member

rvagg commented Jun 15, 2016

Time

UTC Wed 15-Jun-2016 20:00:

  • San Francisco: Wed 15-Jun-2016 13:00
  • New York: Wed 15-Jun-2016 16:00
  • Amsterdam: Wed 15-Jun-2016 22:00
  • Moscow: Wed 15-Jun-2016 23:00
  • Sydney: Thu 16-Jun-2016 06:00
  • Tokyo: Thu 16-Jun-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

  • url: return valid file: urls fom url.format() #7234
  • Tracking issue: stdio problems #6980
  • http: don't inherit from Object.prototype #6102

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.

@jasnell
Copy link
Member

jasnell commented Jun 15, 2016

On vacation this week so I'll be skipping the call. I'm +1 for #7234 and
#6102.
On Jun 15, 2016 4:43 AM, "Rod Vagg" [email protected] wrote:

Time

UTC Wed 15-Jun-2016 20:00:

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

Or in your local time:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2016-06-15&iso=20160615T20

Links

Agenda

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

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
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
https://github.com/orgs/nodejs/teams/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.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7307, or mute the thread
https://github.com/notifications/unsubscribe/AAa2eWz48VJxpD32W3ivuS9T-5r2of_Cks5qL-VngaJpZM4I2RPW
.

@shigeki
Copy link
Contributor

shigeki commented Jun 15, 2016

Apology, I cannot make it this week.

@mikeal
Copy link
Contributor

mikeal commented Jun 15, 2016

I also can't make it :(

@evanlucas
Copy link
Contributor

I may be a few minutes late today.

@Trott
Copy link
Member

Trott commented Jun 15, 2016

Standup section of the doc is now ready to be filled in if you want to save the note-taker some work.

@Fishrock123 Fishrock123 added the meta Issues and PRs related to the general management of the project. label Jun 15, 2016
@Fishrock123
Copy link
Contributor

  • Tracking issue: stdio problems #6980

Removing from the agenda, there isn't much to discuss.

@srl295
Copy link
Member

srl295 commented Jun 15, 2016

Late notice but I should decline- have some (nonliteral) firefighting. Still working on #7253 - working through the cross-compile issues.

@jdalton
Copy link
Member

jdalton commented Jun 15, 2016

I'll be an observer.

@Fishrock123
Copy link
Contributor

Livestream viewers, max concurrent: 11

node_livestream_viewers-2016-06-15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants