Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-11-02 #9392

Closed
Trott opened this issue Nov 1, 2016 · 7 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2016-11-02 #9392

Trott opened this issue Nov 1, 2016 · 7 comments

Comments

@Trott
Copy link
Member

Trott commented Nov 1, 2016

Time

UTC Wed 02-Nov-2016 20:00:

Timezone Date/Time
US / Pacific Wed 02-Nov-2016 13:00
US / Mountain Wed 02-Nov-2016 14:00
US / Central Wed 02-Nov-2016 15:00
US / Eastern Wed 02-Nov-2016 16:00
Amsterdam Wed 02-Nov-2016 21:00
Moscow Wed 02-Nov-2016 23:00
Chennai Thu 03-Nov-2016 01:30
Tokyo Thu 03-Nov-2016 05:00
Sydney Thu 03-Nov-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

nodejs/TSC

  • Consider folding TSC into CTC #146

nodejs/CTC

  • Meeting Schedule #22
  • Review how ctc-review process is working #20

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.

@addaleax
Copy link
Member

addaleax commented Nov 1, 2016

If you don’t mind, I’d like to see if we can get some kind of consensus on #9279?

@Trott
Copy link
Member Author

Trott commented Nov 1, 2016

If you don’t mind, I’d like to see if we can get some kind of consensus on #9279?

Since our governance docs say anyone can add an agenda item, I'd say YES we can totally add it.

Looking at that issue, I see the following opinions on the part of @nodejs/ctc members. (Some of this is interpretation on my part. Correct me if I mention your name and I'm wrong!) I'll also add myself:

+1: @addaleax @evanlucas @ofrobots
-1: @mscdex
0: @cjihrig @bnoordhuis @jasnell @Fishrock123 @Trott

Hopefully other CTC folks can weigh in as to where they currently are with this.

And hopefully all the folks in the +1 and -1 lists can make it to the meeting.

@jasnell
Copy link
Member

jasnell commented Nov 2, 2016

I'm +1 on #9279 at this point

@jasnell
Copy link
Member

jasnell commented Nov 2, 2016

I might not be able to make the meeting today due to a personal scheduling conflict.

@ChALkeR
Copy link
Member

ChALkeR commented Nov 2, 2016

-0 for #9279 atm, but that might change.

@ChALkeR
Copy link
Member

ChALkeR commented Nov 2, 2016

I will most likely be absent today.

+1 on #8558.

@addaleax
Copy link
Member

addaleax commented Nov 2, 2016

I know it’s really last-minute but I think I’d like to take the liberty to invite @targos… any objections?

(edit: sent an email)

@jasnell jasnell closed this as completed Nov 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants