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-02-08 #68

Closed
Trott opened this issue Feb 7, 2017 · 14 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-02-08 #68

Trott opened this issue Feb 7, 2017 · 14 comments

Comments

@Trott
Copy link
Member

Trott commented Feb 7, 2017

Time

UTC Wed 08-Feb-2017 05:00:

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

  • [WIP] meta: update copyright statements #10599
  • [WIP] Restore copyright attribution #10155
  • lib: be robust when process global is clobbered #10135
  • http: support environment-defined proxy #8381

nodejs/TSC

  • Updating the Copyright #174

nodejs/node-eps

  • Rewrite 002 - esm #39

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 Feb 7, 2017

Note that this meeting is in approximately 23 hours. Sorry for the shorter-than-usual notice!

@Trott
Copy link
Member Author

Trott commented Feb 7, 2017

The two work-in-progress PRs for copyright attribution are both labeled ctc-agenda and ctc-review. Can I please remove both of those labels? There's already the "Updating the copyright" issue from the TSC repo that is labeled ctc-agenda. Having that issue show up multiple times week after week is getting irksome and making me (and I imagine others) not really take items that show up on the agenda seriously. Like, "Oh, we probably won't even talk about half of these things." This is not good for the health of the meeting IMO.

@Trott
Copy link
Member Author

Trott commented Feb 7, 2017

Some people were adamant last week that async-vs-sync issue around ES modules interoperability would be brought to a vote this week. If you know how you'd like to vote on that (or if you know you'd like to abstain), please indicate in nodejs/node-eps#39. So far, only @targos has cast a vote. Usually @bmeck is the person to ask if you have questions, but they're on vacation and suggested that @Fishrock123 would be a good go-to person in their absence.

@bnoordhuis
Copy link
Member

bnoordhuis commented Feb 7, 2017

I've removed the ctc-agenda label from nodejs/node#10135. It was discussed two or three weeks ago.

The two work-in-progress PRs for copyright attribution are both labeled ctc-agenda and ctc-review. Can I please remove both of those labels?

Since I was in the process of removing labels anyway, I've removed them from those PRs as well. :-)

@targos
Copy link
Member

targos commented Feb 7, 2017

http: support environment-defined proxy #8381 was also discussed a few weeks ago. I removed the label.

@Trott
Copy link
Member Author

Trott commented Feb 7, 2017

@bnoordhuis @targos Awesome, thanks! That means we have two agenda items for the meeting (async-vs-sync module loader with a vote expected to be called for, and the copyright stuff which is now represented by a single issue).

(@nodejs/ctc There's also the handful of ctc-review issues in the comment above so be sure to check those out.)

@mhdawson
Copy link
Member

mhdawson commented Feb 7, 2017

Not going to be able to make this one given the time.

@misterdjules
Copy link

I won't be able to make this meeting. Hopefully I'll get back on track and start attending meetings again next week.

@Trott
Copy link
Member Author

Trott commented Feb 7, 2017

@mhdawson If you could vote or else abstain on the whole async-vs-sync loader issue in nodejs/node-eps#39, that will hopefully help us get resolution faster.

@bnoordhuis
Copy link
Member

The meeting is three hours from now and I haven't slept yet so I'm probably going to miss out.

W.r.t. to nodejs/node-eps#39: abstain - I don't have an informed enough opinion yet.

@rvagg
Copy link
Member

rvagg commented Feb 8, 2017

ditto on the EPS vote, I've abstained in there

@joshgav
Copy link
Contributor

joshgav commented Feb 8, 2017

I didn't capture next steps for the copyright stuff, I think they're approximately this:

  • James to continue work on node#10599.
  • Keep on agenda for next week to review Board’s decisions.

Will put that in the notes for now, but if you have other suggestions chime in here or in the notes PR when I get it opened. Thanks!

@joshgav
Copy link
Contributor

joshgav commented Feb 8, 2017

Notes in #69.

@joshgav joshgav closed this as completed Feb 8, 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

7 participants