-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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-01-27 #4901
Comments
As quick prep:
Nothing specific, status update and how to move forward on discussion, also re nodejs/roadmap#54
Nothing to cover, leaving this on to make sure we vote soon
Nothing specific, discussion on status and how to move forward
Left on agenda, may not be ready for ratifying yet, will see
There is a tiny bit of movement, I can give a very quick update
This comes from last meeting where we discussed "fs: optimize realpath using uv_fs_realpath() #3594". I believe that a decision to drop XP would make it easier resolve the other question, possibly resulting in libuv 2.0. |
I will be absent for the security assessment work at tomorrow night. I have no objection for #4750. |
regrets, hosting Unicode UTC146 this week |
Apologies for not being able to make it. I was involved in full day discussions around async context propagation and error handling. |
Minutes going in @ #5057 Audio @ https://soundcloud.com/node-foundation/ctc-meeting-2016-01-27 |
Time
UTC Wed 27-Jan-2016 20: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
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.
The text was updated successfully, but these errors were encountered: