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-07-19 #154

Closed
Trott opened this issue Jul 16, 2017 · 16 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-07-19 #154

Trott opened this issue Jul 16, 2017 · 16 comments

Comments

@Trott
Copy link
Member

Trott commented Jul 16, 2017

Time

UTC Wed 19-Jul-2017 16:00 (04:00 PM):

Timezone Date/Time
US / Pacific Wed 19-Jul-2017 09:00 (09:00 AM)
US / Mountain Wed 19-Jul-2017 10:00 (10:00 AM)
US / Central Wed 19-Jul-2017 11:00 (11:00 AM)
US / Eastern Wed 19-Jul-2017 12:00 (noon)
Amsterdam Wed 19-Jul-2017 18:00 (06:00 PM)
Moscow Wed 19-Jul-2017 19:00 (07:00 PM)
Chennai Wed 19-Jul-2017 19:30 (09:30 PM)
Hangzhou Thu 20-Jul-2017 00:00 (midnight)
Tokyo Thu 20-Jul-2017 01:00 (01:00 AM)
Sydney Thu 20-Jul-2017 02:00 (02: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

  • meta: semver impact of Error messages #13937

Invited

Observers

  • Bradley Meck @bmeck (GoDaddy/TC39)
  • Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
  • Josh Gavant @joshgav (Microsoft)
  • Kaitlyn Barnard @kbarnard10 (Node.js Foundation Newsletter Curator)
  • Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)

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.

@guybedford
Copy link

@Trott would it be possible to add an agenda item for the "module" property proposal at https://github.com/nodejs/node-eps/pull/60/files#diff-b193302c6b58f3c92b9098094d833b64R140? It would be really great to be able to open some discussion on the approach.

@fhinkel
Copy link
Member

fhinkel commented Jul 17, 2017

The official calendar shows the meeting as 1 pm pacific time. Did we change the schedule?

@targos
Copy link
Member

targos commented Jul 17, 2017

The calendar must be wrong. The meeting schedule shows 9 am pacific time. I suppose the calendar wasn't updated correctly when we switched to a biweekly meeting.

@Trott
Copy link
Member Author

Trott commented Jul 18, 2017

@Trott would it be possible to add an agenda item for the "module" property proposal at https://github.com/nodejs/node-eps/pull/60/files#diff-b193302c6b58f3c92b9098094d833b64R140? It would be really great to be able to open some discussion on the approach.

@guybedford Anybody can add an item to the agenda, so sure, totally possible. Personally, I'd be inclined to allow more time for general comment and discussion in the pull request before involving the CTC. (That PR has been open for only 4 days.) Would it be OK to instead put it on the agenda for next meeting (in two weeks)?

At this time, I'll certainly do the following:

  • use a PR comment to @-mention some folks who are likely to have opinions so as to see what kinds of feedback we get
  • since EPs do have to be voted on by CTC, add ctc-agenda and ctc-review labels

@Trott
Copy link
Member Author

Trott commented Jul 18, 2017

Can someone with write access to the Google calendar (for all Node.js meetings) fix the meeting time for this week (9AM PDT) and August 2 as well (1PM PDT)? Thanks in advance! /cc @williamkapke @mhdawson

@guybedford
Copy link

@Trott many thanks! My primary goal is mainly just to create an active space here for consideration. Appreciated for the cc's - I'll get back to the initial questions there, but would still value a slot tomorrow if possible, even if it means less time to discuss or go into the details initially.

@mcollina
Copy link
Member

@Trott I have access, and I have update the next ones. If you tell me how these are recurring, I will fix the recurring schedule as well.

@targos
Copy link
Member

targos commented Jul 18, 2017

I think these are recurring like this:

  • 11:00:00 UTC
  • no meeting
  • 16:00:00 UTC
  • no meeting
  • 20:00:00 UTC
  • no meeting
  • 11:00:00 UTC
  • ...

So each different time occurs every 6 week.

@mcollina
Copy link
Member

I updated the recurring events in the calendar. Let me know if they are correct.

@targos
Copy link
Member

targos commented Jul 18, 2017

Recurrence is missing for the 20:00:00 UTC meetings. Apart from that, LGTM.

@mcollina
Copy link
Member

@targos done.

@MylesBorins
Copy link

I would like us to add a general discussion around Turbo-Fan + ignition.. specifically so we can agree on a release plan

I've added ctc-agenda to #155 to reflect this request

@mhdawson
Copy link
Member

I've added ctc-agenda to nodejs/Release#223. Still may need a bit of final tweaking but I think the general scope/wording is close enough to validate that the CTC agrees with chartering the Release WG in this context.

@targos
Copy link
Member

targos commented Jul 19, 2017

I won't be able to attend today's meeting. My apologies.

@addaleax
Copy link
Member

I’ll very likely be late again, maybe 20 – 30 min, but I should be able to show up (and would really like to).

@Trott Trott closed this as completed Jul 31, 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