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-02-17 #5274

Closed
rvagg opened this issue Feb 17, 2016 · 5 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-02-17 #5274

rvagg opened this issue Feb 17, 2016 · 5 comments

Comments

@rvagg
Copy link
Member

rvagg commented Feb 17, 2016

Time

UTC Wed 17-Feb-2016 20:00:

  • San Francisco: Wed 17-Feb-2016 12:00
  • New York: Wed 17-Feb-2016 15:00
  • Amsterdam: Wed 17-Feb-2016 21:00
  • Moscow: Wed 17-Feb-2016 23:00
  • Sydney: Thu 18-Feb-2016 07:00
  • Tokyo: Thu 18-Feb-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

  • Issue management: discuss caine again #5246
  • refactor src/node.js into internal files #5103
  • process: add 'warn' event #4782
  • CTC Membership Nominations #4750
  • buffer: add Buffer.from(), Buffer.alloc() and Buffer.allocUnsafe(), soft-deprecate Buffer(num) #4682 & Buffer(number) is unsafe #4660

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.

@rvagg
Copy link
Member Author

rvagg commented Feb 17, 2016

I've removed the legal advice item off this as there are no updates this week. The CTC nominations item is left in and I've proposed votes for next week.

@indutny @trevnorris @jasnell please come prepared to discuss the issues you've labelled. Everyone else: please try and familiarise yourself with those issues before the meeting if you can.

@rvagg rvagg closed this as completed Feb 24, 2016
@mikeal
Copy link
Contributor

mikeal commented Feb 24, 2016

I'm on a plane so I won't be on this one :(

@ChALkeR
Copy link
Member

ChALkeR commented Feb 24, 2016

@mikeal, perhaps you meant #5409?

@mikeal
Copy link
Contributor

mikeal commented Feb 24, 2016

@ChALkeR I did :) too late now, but thanks :)

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

4 participants