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-22 #7366

Closed
rvagg opened this issue Jun 22, 2016 · 12 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-06-22 #7366

rvagg opened this issue Jun 22, 2016 · 12 comments

Comments

@rvagg
Copy link
Member

rvagg commented Jun 22, 2016

Time

UTC Wed 22-Jun-2016 20:00:

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

  • Node 6 fs.realpath behavior changes #7175

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.

@ofrobots
Copy link
Contributor

I have a conflict for the first half hour. I will join after that.

@Fishrock123
Copy link
Contributor

Vacation this week.

Re: realpath - we need to have some option for modules to use.

@orangemocha
Copy link
Contributor

I am on vacation this week and the next.

@indutny
Copy link
Member

indutny commented Jun 22, 2016

I have a schedule conflict, may not be able to join you today. Sorry!

@jhamhader
Copy link
Contributor

Will attend the IRC and listen to the live meeting for the realpath discussion.

@srl295
Copy link
Member

srl295 commented Jun 22, 2016

i have a conflict for the last 30 minutes, but will join for the first 30.

@Trott
Copy link
Member

Trott commented Jun 22, 2016

Standup portion of the doc is ready for anyone wanting to update it before the meeting.

@ChALkeR
Copy link
Member

ChALkeR commented Jun 22, 2016

I will probably skip this week, not feeling very well today.

The only thing I wanted to note about #7175 is that simply reverting #3594 would be a semver-major change, as it will break the encoding option, so the fix (if any) would have to take that into an account.

@jdalton
Copy link
Member

jdalton commented Jun 22, 2016

I'll be attending to give an update on the UnambiguousJavaScriptGrammar ES module proposal which was introduced last week.

@rvagg
Copy link
Member Author

rvagg commented Jun 22, 2016

Please go ahead without me. I've woken up to find I have a sick child to deal with.

@Trott
Copy link
Member

Trott commented Jun 22, 2016

No live stream today. Apologies to everyone listening/waiting. It is being recorded and I hope/imagine that @rvagg (or someone else) will be able to edit and post audio at a later date.

@benjamingr
Copy link
Member

@Trott I would be interested in @jdalton's introduction - but minute notes would be fine.

joshgav added a commit to joshgav/node that referenced this issue Jun 23, 2016
@jasnell jasnell closed this as completed Jul 3, 2016
jasnell pushed a commit that referenced this issue Aug 1, 2016
closes #7366

PR-URL: #7390
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
cjihrig pushed a commit that referenced this issue Aug 10, 2016
closes #7366

PR-URL: #7390
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this issue Sep 30, 2016
closes #7366

PR-URL: #7390
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
rvagg pushed a commit that referenced this issue Oct 18, 2016
closes #7366

PR-URL: #7390
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this issue Oct 26, 2016
closes #7366

PR-URL: #7390
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
Reviewed-By: James M Snell <[email protected]>
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.