Node Foundation TSC Meeting 2015-06-24 about node-convergence-archive HOT 5 CLOSED

Imma give my apologies for not attending tomorrow, I've had to choose between two meetings and this one lost out this time around, sorry. Uberconference will record automatically, I'll ship the mp3 off to @mikeal as soon as it's done and he can edit and upload to soundcloud.

Also, we've been toying with bluejeans.com @ NodeSource as an alternative to Uberconference & Hangouts and so far it's promising. I've yet to see its broadcast features but I plan on diving in to it soon and will come back with a recommendation. The lack of live-stream-ability really bothers me with Uberconference, it disconnects the TSC too much from the other collaborators, plus we haven't been good at noting Soundcloud links (we should remember to put them in minutes afterward) so the meetings are a fairly isolated event.

from node-convergence-archive.

My regrets as well, due to similar competing-meeting reasons with some TAG stuff.

from node-convergence-archive.

I won't be able to attend this time, but I'll catch up with the meeting's minutes.

from node-convergence-archive.

One additional agenda item would add re: joyent/node is our strategy
regarding Feature Requests in the issue tracker. I've gone through most of
the issues tagged as Feature Requests and managed to close a good number,
but we need to decide on the basic strategy -- (a) do we close them and ask
that people open new issues against nodejs/node or nodejs/io.js, (b) do we
just close them without any further action or (c) do we keep them open for
tracking purposes?

On Wed, Jun 24, 2015 at 4:05 AM, Rod Vagg [email protected] wrote:

Time

UTC Wed 24-Jun-15 20:00:

• San Francisco: Wed 24-Jun-15 13:00
• Amsterdam: Wed 24-Jun-15 22:00
• Moscow: Wed 24-Jun-15 23:00
• Sydney: Thu 25-Jun-15 06:00

Or in your local time:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node+Foundation+TSC+Meeting+2015-06-24&iso=20150624T20

• or
  http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jun+24%2C+2015+in+local+time

Links

• GitHub Issue: #58 nodejs/node#58
• Original Minutes Google Doc: hhttps://
  docs.google.com/document/d/1T12-WeLzO_rqs_2BloM2O-f_RrN0OWzfaQVCKjGYKrc

Attendees will be given a conference number to dial in to.
Agenda

Extracted from tsc-agenda labelled issues and pull requests prior to
meeting.
nodejs/node nodejs/io.js

• discussion of stability for internal APIs #2030
  nodejs/node#2030

joyent/node

• Nominating new collaborators to this repository #25481
  nodejs/node-v0.x-archive#25481

Invited

• @bnoordhuis https://github.com/bnoordhuis (TSC)
• @chrisdickinson https://github.com/chrisdickinson (TSC)
• @cjihrig https://github.com/cjihrig (TSC)
• @domenic https://github.com/domenic (observer)
• @Fishrock123 https://github.com/Fishrock123 (TSC)
• @indutny https://github.com/indutny (TSC)
• @isaacs https://github.com/isaacs (TSC)
• @jasnell https://github.com/jasnell (TSC)
• @mhdawson https://github.com/mhdawson (TSC)
• @misterdjules https://github.com/misterdjules (TSC)
• @mikeal https://github.com/mikeal (website)
• @mscdex https://github.com/mscdex (TSC)
• @orangemocha https://github.com/orangemocha (TSC)
• @piscisaureus https://github.com/piscisaureus (TSC)
• @rvagg https://github.com/rvagg (TSC)
• @shigeki https://github.com/shigeki (TSC)
• @srl295 https://github.com/srl295 (TSC)
• @trevnorris https://github.com/trevnorris (TSC)

Notes

The agenda now comes from issues labelled with tsc-agenda in all 3
repositories listed above. Please label any additional issues that should
be on the agenda before the meeting starts. I'm using a tool
https://github.com/rvagg/iojs-tools/tree/master/tsc-meeting-agenda to
fetch the list so it's not a big deal to collate.

This meeting will be held via Uberconference. No live streaming this time
unfortunately. Leave questions you want answered by the TSC in this thread
as there won't be a QA.

The recording will go up on Soundcloud straight afterwards.

—
Reply to this email directly or view it on GitHub
nodejs/node#58.

from node-convergence-archive.

@jasnell In the past we've tried to keep the feature requests present in joyent/node open on joyent/node (i.e., we don't port them to new repos, like io.js; but we also don't close them if they haven't been finished yet.) If folks want to work on a feature request from one of the old repos they should open a new issue or PR on nodejs/node linking to the old issue(s).

from node-convergence-archive.