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 2017-01-18 #61

Closed
Trott opened this issue Jan 15, 2017 · 7 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-01-18 #61

Trott opened this issue Jan 15, 2017 · 7 comments

Comments

@Trott
Copy link
Member

Trott commented Jan 15, 2017

Time

UTC Wed 18-Jan-2017 05:00:

Timezone Date/Time
US / Pacific Tue 17-Jan-2017 21:00
US / Mountain Tue 17-Jan-2017 22:00
US / Central Tue 17-Jan-2017 23:00
US / Eastern Wed 18-Jan-2017 00:00
Amsterdam Wed 18-Jan-2017 06:00
Moscow Wed 18-Jan-2017 08:00
Chennai Wed 18-Jan-2017 10:30
Tokyo Wed 18-Jan-2017 14:00
Sydney Wed 18-Jan-2017 16: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

  • Proposal to move guides to nodejs/nodejs.org #10792
  • [WIP] meta: update copyright statements #10599
  • [WIP] Restore copyright attribution #10155
  • process: Add code to warnings, assign codes to deprecations #10116
  • meta: deprecation policy #7964
  • lib: be robust when process global is clobbered #10135

nodejs/TSC

  • Bring 'node-inspect' (CLI Debugger) under the Foundation #190
  • Updating the Copyright #174

nodejs/node-eps

  • Rewrite 002 - esm #39

nodejs/CTC

  • Growing the group of releasers #48

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.

@Trott
Copy link
Member Author

Trott commented Jan 15, 2017

Note that this meeting is at a time we haven't used before. Especially if you are in the Americas, carefully note the date too! It will be Tuesday night (or, if on Eastern time, "midnight Wednesday" which is effectively late Tuesday night)!

@italoacasas
Copy link

Is this something y'all want to discuss and make a decision? nodejs/node#10574

@s3ththompson
Copy link

Unfortunately, I'll be unable to attend this meeting.

@MylesBorins
Copy link

MylesBorins commented Jan 17, 2017 via email

@bmeck
Copy link
Member

bmeck commented Jan 18, 2017

I'd like nodejs/node#10135 discussed as to why just process and why non-writable. Many global references are essential for node to function: https://github.com/bmeck/node/blob/no-globals/lib/internal/globals.js

@rvagg
Copy link
Member

rvagg commented Jan 18, 2017

@italoacasas I think that discussion might need to mature more on GitHub, there doesn't seem to be any movement since @mscdex' objection so I'm not seeing a need to escalate it yet.

@bmeck added to agenda as a discussion point, since you did flag it a few days ago.

@evanlucas
Copy link

sorry yall, I slept through my alaram :[

@jasnell jasnell closed this as completed Jan 25, 2017
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

8 participants