io.js TC Meeting 2015-02-04

[rvagg]

UTC Wed 04-Feb-15 19:00:

• San Francisco: Wed 04-Feb-15 11:00
• Amsterdam: Wed 04-Feb-15 20:00
• Moscow: Wed 04-Feb-15 22:00
• Sydney: Thu 05-Feb-15 06:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=io.js+TC+Meeting+2015-02-04&iso=20150204T19&p1=1440&ah=1
• or http://www.wolframalpha.com/input/?i=7pm+UTC%2C+February+4%2C+2015+in+local+time

Please allow time for cat-herding before broadcast starts.

Public YouTube feed: http://www.youtube.com/watch?v=IhXa2FmtBI4
Google Plus Event page: https://plus.google.com/u/1/b/101986715696875566237/events/cfn4cq32ukvsd4lqm7doe30gppo

Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC, streams), @cjihrig (TC), @mikeal (website), @rvagg (build, streams), @domenic (observer)

Agenda and minutes doc, editable by TC, commentable by everyone else: https://docs.google.com/document/d/1a75PUmyTXsLmoMAUCDPRPSQEBGt0XDgZAzKpAYeRUEQ (written in markdown so we can put it straight into the repo)

Agenda so far: lifted from issues marked with _tc-agenda_, please label, or ask to have issues labelled if they need to be elevated to TC discussion.

• assert: don't compare object prototype property #636 and assert: introduce deepStrictEqual #639 / @vkurchatkin
• Release PGP key strategy and policy #709 / @rvagg

[vkurchatkin]

Labeled #636 and #639 as tc-agenda if no one objects. I thinks the questions to discuss are:

• the future of assert module;
• relationship between assert and CommonJS Unit Testing spec;
• particular assert: don't compare object prototype property #636 bug;
• what "deep equality" means and how it should deal with prototypes;
• assert: introduce deepStrictEqual #639 proposal.

[rvagg]

@vkurchatkin can you elaborate a little on where you'd like this discussion to go? The questions in the PRs are fairly narrow in scope, i.e. do we merge these, but you're pointing to a broader discussion about 'assert'. I suspect that some discussion might circle around how far we're willing to break with joyent/node on this but perhaps if you have a larger vision for the future of 'assert' you should outline that so the discussion can be focused on that. It could be (I'm not speaking from authority here by any means) that nobody else really wants to step up and own that module and the TC are willing to let you steer it a little because you seem to be expressing the strongest opinions about its future, but you'd first need to outline the guiding principles. If it's more than a paragraph or two perhaps a new issue for discussion.

[vkurchatkin]

@rvagg I don't have any strong opinions about assert, I just want this module to be useful and adequate. #636 I consider a bugfix, #639 a really important feature (see nodejs/node-v0.x-archive#7161). But some people have expressed opinions about assert being bound to CommonJS. Quote from @indutny:

assert module has stability 5 - locked and is implemented upon CommonJS standard: http://wiki.commonjs.org/wiki/Unit_Testing/1.0 . If you have any ideas - please try submitting them to CommonJS guys first!

I want TC to clarify if this is still true. If it is, assert should probably be deprecated.

[timoxley]

assert should probably be deprecated

Why

[vkurchatkin]

because CommonJS spec is broken and umaintained

[Fishrock123]

If there's a lack of stuff to discuss, the promise-api threads got a bunch more attention recently.

[Fishrock123]

@srl295 sends his apologies for being unable to attend at this time. (see also: #565 (comment))