Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Node Foundation TSC Meeting 2015-10-07 #3234

Closed
rvagg opened this issue Oct 7, 2015 · 13 comments
Closed

Node Foundation TSC Meeting 2015-10-07 #3234

rvagg opened this issue Oct 7, 2015 · 13 comments

Comments

@rvagg
Copy link
Member

rvagg commented Oct 7, 2015

Time

_NOTE the time may have changed in your local timezone due to daylight savings shifts_

UTC Wed 07-Oct-2015 20:00:

  • San Francisco: Wed 07-Oct-2015 13:00
  • Amsterdam: Wed 07-Oct-2015 22:00
  • Moscow: Wed 07-Oct-2015 23:00
  • Sydney: Thu 08-Oct-2015 07:00
  • Tokyo: Thu 08-Oct-2015 05:00

Or in your local time:

Links

Agenda

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

nodejs/node

  • WG: Considering a new HTTP WG #3214
  • lib,test: deprecate _linklist #3078
  • Discussion: LTS & v5 release planning #3000
  • Compiling node v4.0.0 with OpenSSL 1.0.1 fails #2783
  • Inspecting Node.js with Chrome DevTools #2546

nodejs/TSC

  • Umbrella Program #2

Invited

Notes

The agenda comes from issues labelled with across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts. I'm using a tool to fetch the list so it's not a big deal to collate.

Joining the meeting

Uberconference; participants should have the link & numbers, contact me if you don't.
@orangemocha
Copy link
Contributor

Apologies... I most likely won't be able to make it today.

@jasnell
Copy link
Member

jasnell commented Oct 7, 2015

Unfortunately I just realized I have a conflict as well. Which is
unfortunate. I'll try to join towards the later half of the call.
On Oct 7, 2015 10:27 AM, "Alexis Campailla" notifications@github.com
wrote:

Apologies... I most likely won't be able to make it today.

—
Reply to this email directly or view it on GitHub
#3234 (comment).

@piscisaureus
Copy link
Contributor

We're having a company all-hands - I won't be able to make it today either.

@mikeal
Copy link
Contributor

mikeal commented Oct 7, 2015

Wow, how big is the IBM all hands? Do you just rent a small country? :)

On Oct 7, 2015, at 11:07AM, Bert Belder notifications@github.com wrote:

We're having a company all-hands - I won't be able to make it today either.

—
Reply to this email directly or view it on GitHub #3234 (comment).

@jasnell
Copy link
Member

jasnell commented Oct 7, 2015

Heh, StrongLoop all hands, not IBM all hands ;-)

@mikeal
Copy link
Contributor

mikeal commented Oct 7, 2015

@jasnell ahh, much more reasonable :)

@jasnell
Copy link
Member

jasnell commented Oct 7, 2015

Very unfortunate that I won't be able to make the call today given that two of the agenda items are mine. Here are my thoughts to seed the discussion:

  1. For the HTTP WG, the goal is for the WG to take ownership of the HTTP functionality in exactly the same way that the Streams WG has taken ownership over the Streams module. There are no immediate plans to change anything in the existing API but a key part of the discussion and focus will be to evaluate what, if anything, may need to be evolved over time to better support the ecosystem. Pulling the express and hapi developers into that discussion as much as possible is key to the success of the WG. We have an initial meeting in the planning and already have Eran and Doug participating in the discussions.
  2. For the OpenSSL 1.0.1 v 1.0.2 discussion. I think we're pretty much settled that there's nothing that can be done unless someone steps up with a shim that would allow Node to be dynamically linked against 1.0.1 without loss of functionality. Regardless if that gets written or not, it likely would never be supported by core and would need to be an extra thing. So there's likely not much to do here. But, it would be good to get an official decision from the TSC on it.
  3. For LTS timing, my goal is to have the time tonight and tomorrow to help start putting that release together. Hopefully after the next few hours of phone calls I'll actually be able to get to it.

@mikeal
Copy link
Contributor

mikeal commented Oct 7, 2015

Because we were missing quite a few people we're doing the vote on the umbrella program in this thread. Please, all @nodejs/tsc give a +1 or -1.

nodejs/TSC#2

The only immediate result of this will be that responsibility for Core, and most of the WGs, will move to the Core TLP. No other projects are being accepted yet.

@indutny
Copy link
Member

indutny commented Oct 7, 2015

+1

@rvagg
Copy link
Member Author

rvagg commented Oct 8, 2015

Audio for this call is available @ https://soundcloud.com/node-foundation/tsc-meeting-2015-10-07

@trevnorris
Copy link
Contributor

@mikeal does approving the umbrella program here also approve the linked PR?

@mikeal
Copy link
Contributor

mikeal commented Oct 8, 2015

@trevnorris it approves it pending any style changes people throw in that thread, so long as you don't take issue with the content :)

@trevnorris
Copy link
Contributor

@mikeal I'm cool with the content, definitely has style issues. ;-)

@rvagg rvagg closed this as completed Oct 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@mikeal @mscdex @piscisaureus @indutny @trevnorris @jasnell @rvagg @orangemocha