-
Notifications
You must be signed in to change notification settings - Fork 27
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-03-01 #74
Comments
FYI, I just left a comment on #9276 Symbol key props visible in inspection by default that might result in it landing on the agenda this week. |
I've removed the label from nodejs/node#11200, that one was settled a couple of weeks ago. |
Just a reminder, since some of us are still probably not quite used to this time due to the "OMG it's on Tuesday?" factor for much of North America: The CTC meeting is in less than 24 hours. |
I'm not going to be able to make it this week, too late for me. |
Not likely to make it tonight.
…On Feb 28, 2017 11:57 AM, "Gibson Fahnestock" ***@***.***> wrote:
@Trott <https://github.com/Trott> Just a reminder to mention #58
<#58> (giving collaborators access to
the help repo)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#74 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV5WmKVpO_3JYMItqzvgYnZDm4hDPks5rhFHrgaJpZM4MNIfs>
.
|
Not likely to make it. |
For the folks who cannot make it tonight, could I ask that you leave a comment indicating your position on each of the agenda items (even if it's "no position" ... :-) ...) |
I probably won't make it tonight either... |
I think you mean the ctc-review items instead. (There's only two agenda items and neither involve CTC taking a position on something.) Regardless, yeah, if everyone could look those over, that would rock. |
Mad props to @jasnell for taking action on a whole bunch of stale issues and PRs. 🤘 (Not really specific to CTC or the meeting, but good community stewardship certainly isn't unrelated to CTC...) |
notes in #75. goodnight! |
Time
UTC Wed 01-Mar-2017 05:00 (05:00 AM):
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
nodejs/TSC
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: