-
Notifications
You must be signed in to change notification settings - Fork 27
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-02-08 #68
Comments
Note that this meeting is in approximately 23 hours. Sorry for the shorter-than-usual notice! |
The two work-in-progress PRs for copyright attribution are both labeled |
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. |
I've removed the ctc-agenda label from nodejs/node#10135. It was discussed two or three weeks ago.
Since I was in the process of removing labels anyway, I've removed them from those PRs as well. :-) |
http: support environment-defined proxy #8381 was also discussed a few weeks ago. I removed the label. |
@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 |
Not going to be able to make this one given the time. |
I won't be able to make this meeting. Hopefully I'll get back on track and start attending meetings again next week. |
@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. |
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. |
ditto on the EPS vote, I've abstained in there |
I didn't capture next steps for the copyright stuff, I think they're approximately this:
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! |
Notes in #69. |
Time
UTC Wed 08-Feb-2017 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
[WIP] meta: update copyright statements #10599[WIP] Restore copyright attribution #10155lib: be robust when process global is clobbered #10135http: support environment-defined proxy #8381nodejs/TSC
nodejs/node-eps
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.
The text was updated successfully, but these errors were encountered: