Node Foundation TSC Meeting 2015-10-07

Present

Extracted from tsc-agenda labelled issues and pull requests in the nodejs org prior to meeting.

Rod Vagg: 4.1.2 release, security procedures surrounding that
Brian White: Working on javascript dns resolver, regular PR + Issue work.
Steven Loomis: Working on ICU 56 Release. TC 39 & emca spec work for Intl WG. Working on Intl build issues.
Trevor Norris: Focused on fixing async_wrap, writing tests and preparing for it to become more official
Shigeki Ohtsu: No works for node project, I spent all time to my internal works.
Ben Noordhuis: Nothing to report—the usual
Mikeal Rogers: Looking into stalled Wgs and seeing how to help out. Working on the umbrella program. Lots of conference things.
Michael Dawson: Added a benchmarking machine to the CI, working on some tests issues. Working on PPC for the CI.
Seth Thompson: Working on v8 4.7, scheduled soon
Jeremiah Senkpiel: vacation, some issue catch-up

Discussed the HTTP WG based on James’ comments @ https://github.com/nodejs/node/issues/3234#issuecomment-146293038
Generally positive, only concerns are regarding decision making power—TSC may not want to hand that off as this is not quite like Streams (in that few people grok the code!) and there are philosophical questions to be resolved about HTTP that the TSC should be involved in.

Userland modules exist that could be used instead
Ben suggested straight removal, Jeramiah raised the matter of process that we have committed to adding a warning before removal, so we could remove in v6 but probably shouldn’t in v5
No disagreement with moving forward for deprecation

Recap of the latest LTS meeting LTS#43
Aim to have LTS / v4.2.0 out tomorrow, backup date of Monday if we miss that. LTS starts then for v4.x, v5.x has to wait until V8 4.6 to be stable mid to late October.

Shigeki, Ben: It would be quite hard to support 1.0.1 since we are using 1.0.2 APIs.
Discussion on the possible difficulty of using 1.0.2 on varied Linux distros
ubuntu wily (not released) seems to use 1.0.2 - work has been done to package. 1.0.2 is only in Wily - https://launchpad.net/ubuntu/+source/openssl/1.0.2d-0ubuntu1 - https://answers.launchpad.net/ubuntu/+source/openssl/+question/263725 - “My guess is that we will see openssl 1.0.2 from Ubuntu 15.10 onwards (or eventually only starting with 16.04)”
Concern that allowing 1.0.1 would result in a substandard (insecure?) & untested binary.
Some discussion about the fact that we don’t test building with shared / static dependencies
feedback to issue: No appetite to do the work from the TSC, maybe someone could do it but we wouldn’t support.

skipped discussion

skipped discussion

October 14th, 2015