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-06-28 #148

Closed
Trott opened this issue Jun 25, 2017 · 9 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-06-28 #148

Trott opened this issue Jun 25, 2017 · 9 comments

Comments

@Trott
Copy link
Member

Trott commented Jun 25, 2017

Time

UTC Wed 28-Jun-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Wed 28-Jun-2017 13:00 (01:00 PM)
US / Mountain Wed 28-Jun-2017 14:00 (02:00 PM)
US / Central Wed 28-Jun-2017 15:00 (03:00 PM)
US / Eastern Wed 28-Jun-2017 16:00 (04:00 PM)
Amsterdam Wed 28-Jun-2017 22:00 (10:00 PM)
Moscow Wed 28-Jun-2017 23:00 (11:00 PM)
Chennai Thu 29-Jun-2017 01:30 (01:30 AM)
Hangzhou Thu 29-Jun-2017 04:00 (04:00 AM)
Tokyo Thu 29-Jun-2017 05:00 (05:00 AM)
Sydney Thu 29-Jun-2017 06:00 (06: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.

Invited

Observers

  • Bradley Meck @bmeck (GoDaddy/TC39)
  • Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
  • Josh Gavant @joshgav (Microsoft)
  • Mikeal Rogers @mikeal (Node.js Foundation Community Manager)
  • Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
  • Jenn Turner @renrutnnej (Node.js Foundation Newsletter Curator)

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 Jun 25, 2017

No agenda items as of now. If you have something, leave a comment. Otherwise, likely to cancel again!

@bnoordhuis
Copy link
Member

Removed the ctc-review label from issues that had it for > ~2 months and struck them through in Rich's comment.

@refack
Copy link

refack commented Jun 25, 2017

I don't think it's worth holding the meeting just for this, but there's an issue IMHO you should discuss (even next week): The semverity of changing messages in the new Errors.
There have been arguments pro and against marking message change as semver-major, but currently it seems like there is no explicit decision...
Ref: nodejs/node#13730 (comment) & nodejs/node#13730 (comment)
Ref2: nodejs/node#13834 (comment)

@mhdawson
Copy link
Member

@refack does it make sense to open an issue specifically to discuss your question on messages/semver major and add ctc-review? That asks that CTC members weigh on the subject and then we can elevate to ctc-review if we don't see progress in the issue.

@refack
Copy link

refack commented Jun 26, 2017

@refack does it make sense to open an issue specifically to discuss your question on messages/semver major and add ctc-review? That asks that CTC members weigh on the subject and then we can elevate to ctc-review if we don't see progress in the issue.

Yes. On it.

@refack
Copy link

refack commented Jun 26, 2017

nodejs/node#13937 — meta: semver impact of Error messages

@Trott
Copy link
Member Author

Trott commented Jun 27, 2017

This sure seems like the meeting should be canceled. Closing, Feel free to comment or re-open if you think we should have the meeting.

@Trott Trott closed this as completed Jun 27, 2017
@jasnell
Copy link
Member

jasnell commented Jun 27, 2017

Interestingly... I think this would be the third CTC meeting in a row....

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

5 participants