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.

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

Node Foundation TSC Meeting 2015-08-26 #2560

Closed
rvagg opened this issue Aug 26, 2015 · 6 comments
Closed

Node Foundation TSC Meeting 2015-08-26 #2560

rvagg opened this issue Aug 26, 2015 · 6 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@rvagg
Copy link
Member

rvagg commented Aug 26, 2015

Time

UTC Wed 26-Aug-15 20:00:

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

Or in your local time:

Links

Agenda

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

joyent/node

  • Update README to reflect move to nodejs/node #25897

nodejs/node

  • doc: merge CHANGELOG.md with joyent/node ChangeLog #2536
  • (guidance on) rename of "language groups" from iojs-* to nodejs-*? #2525
  • Node.js v4 Release Timeline #2522

Invited

Notes

The agenda comes from issues labelled with tsc-agenda 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.

@mscdex mscdex added tsc-meeting meta Issues and PRs related to the general management of the project. labels Aug 26, 2015
@domenic
Copy link
Contributor

domenic commented Aug 26, 2015

Do we think #2546 is worth TSC discussion yet or still need some time on-thread to bake?

@trevnorris
Copy link
Contributor

@domenic I think there are a couple points of interest for discussion that will be the same in the future. Specifically needing to fully support web sockets, and the API changes that will be necessary.

@jasnell
Copy link
Member

jasnell commented Aug 26, 2015

@domenic ... It's definitely worthy of attention, but I'd be happy to let the conversation stew a bit more before bringing it up to the TSC.

@chrisdickinson
Copy link
Contributor

Sending my apologies today.

@jasnell
Copy link
Member

jasnell commented Aug 26, 2015

I'm going to have to send my regrets for today also. On the way to pick up
a sick kid from school.
On Aug 26, 2015 11:21 AM, "Chris Dickinson" [email protected]
wrote:

Sending my apologies today.


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

@domenic
Copy link
Contributor

domenic commented Aug 26, 2015

Hmm my regrets as well, I have a conflicting meeting... sorry to miss this, sounds like it's going to be an interesting one with the v4 release planning and such.

@rvagg rvagg closed this as completed Aug 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

No branches or pull requests

6 participants