Repository navigation
Node.js Foundation Core Technical Committee (CTC) Meeting 2017-06-28 #148
Description
Activity
No agenda items as of now. If you have something, leave a comment. Otherwise, likely to cancel again!
Items labeled for
ctc-review; @nodejs/ctc please take a look:- Invert dependency between core and readable-stream
lib,src: exit process on unhandled promise rejection cleanupConfirmation that the stability definition is correct- ~lib,src: eagerly exit process on unhanded promise rejections~~
- repl: make REPLServer.bufferedCommand private
- promises: more robust stringification
Removed the ctc-review label from issues that had it for > ~2 months and struck them through in Rich's comment.
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 assemver-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)@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 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.
nodejs/node#13937 — meta: semver impact of Error messages
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.
Reacted by Anna HenningsenReacted by Colin Ihrig and Nikita SkovorodaInterestingly... I think this would be the third CTC meeting in a row....
Time
UTC Wed 28-Jun-2017 20:00 (08:00 PM):
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
Notes
The agenda comes from issues labelled with
ctc-agendaacross 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.