Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-12-28 #51

Closed
Trott opened this issue Dec 26, 2016 · 5 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-12-28 #51

Trott opened this issue Dec 26, 2016 · 5 comments

Comments

@Trott
Copy link
Member

Trott commented Dec 26, 2016

Time

UTC Wed 28-Dec-2016 20:00:

Timezone Date/Time
US / Pacific Wed 28-Dec-2016 12:00
US / Mountain Wed 28-Dec-2016 13:00
US / Central Wed 28-Dec-2016 14:00
US / Eastern Wed 28-Dec-2016 15:00
Amsterdam Wed 28-Dec-2016 21:00
Moscow Wed 28-Dec-2016 23:00
Chennai Thu 29-Dec-2016 01:30
Tokyo Thu 29-Dec-2016 05:00
Sydney Thu 29-Dec-2016 07: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

  • deps: upgrade npm to 4.0.5 #10330
  • console.log and util.format should support the %i integer conversion #10292
  • timers: cleanup extraneous property on Immediates #10205
  • [WIP] Restore copyright attribution #10155
  • process: Add code to warnings, assign codes to deprecations #10116

nodejs/TSC

  • Updating the Copyright #174

nodejs/CTC

  • CTC Meeting Times for 2017 #49

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.

@evanlucas
Copy link

I won't be attending today. I'm on vacation. I will be back next week though. Thanks!

@Trott
Copy link
Member Author

Trott commented Dec 28, 2016

For anyone who won't be at today's meeting, it would be great if you could weigh in on #49.

@ChALkeR
Copy link
Member

ChALkeR commented Dec 28, 2016

It looks like I will miss today, sorry.

If voting happens today, I abstain on nodejs/TSC#174 and nodejs/node#10155, also I already stated my opinion on #49.

As for the remaining issues I will try to comment on GitHub.

@jasnell
Copy link
Member

jasnell commented Dec 28, 2016

FYI... I've made no further progress on updating the PR for nodejs/node#10155 and nodejs/TSC#174 simply because rather than doing that I chose to take some time off and spend a bit more time with the family :-)... there's really nothing further to discuss on those at this point until I get the PR updated, which I will do by the CTC call next week.

@rvagg
Copy link
Member

rvagg commented Dec 28, 2016

Quick discussion, we didn't have streaming and only had a small group. Important topics we briefly covered were:

  • Meeting times - we believe we have enough weigh-ins to move forward there now
  • npm v4 - Myles will take lead on merging that in master and trying to move forward on resolving the do-we-backport question. We've previously agreed (at least those that were in a meeting 2 weeks ago) that the deprecation warnings would be good to get in front of people asap and that the delta was probably small enough to not cause too much drama. One outstanding question is whether the lack of support for partial-shrinkwrap is going to be a problem for anyone, it's possible that Hapi is impacted. So we're researching there.

@rvagg rvagg closed this as completed Dec 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants