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-07-06 #7558

Closed
rvagg opened this issue Jul 6, 2016 · 7 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-07-06 #7558

rvagg opened this issue Jul 6, 2016 · 7 comments

Comments

@rvagg
Copy link
Member

rvagg commented Jul 6, 2016

Time

UTC Wed 06-Jul-2016 20:00:

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

  • build: drop support for VS 2013 in v7 #7484
  • Node 6 fs.realpath behavior changes #7175

nodejs/node-eps

  • AsyncWrap public API proposal #18
  • Replace section 5.1 with unambiguous JavaScript grammar. #33

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 Jul 6, 2016

Folks, please be prepared to discuss AsyncWrap today, the doc is very clear and there only remains some fairly minor nits that @trevnorris may be able to sort out today, or may be able to remain as pending TODOs that we make a prerequisite for accepting the EP.

@rvagg
Copy link
Member Author

rvagg commented Jul 6, 2016

Added:

  • Replace section 5.1 with unambiguous JavaScript grammar. #33

The plan was to try and get a vote on this one as well. Please see the text for updates on the proposal as it also includes a get-out-of-jail card if TC39 doesn't play along, so it should be more palatable.

@jdalton
Copy link
Member

jdalton commented Jul 6, 2016

I'll be there as an observer.

@jasnell
Copy link
Member

jasnell commented Jul 6, 2016

I'd also like to have a short discussion about nodejs/node-eps#28

@Trott
Copy link
Member

Trott commented Jul 6, 2016

Standup section of the doc is ready for your contributions!

@srl295
Copy link
Member

srl295 commented Jul 6, 2016

regrets… 

@bmeck
Copy link
Member

bmeck commented Jul 6, 2016

I'm out on vacation.
On Jul 6, 2016 2:51 PM, "Steven R. Loomis" notifications@github.com wrote:

regrets…


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#7558 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAOUo1i7EXHu7xce3AYR5Yii9x9-kMq7ks5qTAc_gaJpZM4JGADA
.

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

Successfully merging a pull request may close this issue.

7 participants