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

io.js TC Meeting 2015-04-29 #1557

Closed
rvagg opened this issue Apr 29, 2015 · 12 comments
Closed

io.js TC Meeting 2015-04-29 #1557

rvagg opened this issue Apr 29, 2015 · 12 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@rvagg
Copy link
Member

rvagg commented Apr 29, 2015

UTC Wed 29-Apr-15 20:00:

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

Or in your local time:

Please allow time for cat-herding before broadcast starts.

Public YouTube feed: http://www.youtube.com/watch?v=-e675TT4WEA
Google Plus Event page: https://plus.google.com/events/cei87pqnichrtt4qggbbo656bpk
Google Doc for minutes: https://docs.google.com/document/d/1C9nfm_5EhNz1jifITbtQcnGBX4R9vktoZ9KsFiCU7sQ (written in markdown so we can put it straight into the repo)

Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC, streams), @mikeal (website), @rvagg (TC), @domenic (observer), @Fishrock123 (TC), @shigeki (observer), @mscdex (observer)

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.

  • #1532 Release proposal: v2.0.0
  • #1413 Combined node.js/io.js TC/Core Call

Note: There will be time at the end of the meeting for interactive QA with people in the #io.js channel on Freenode.

@rvagg
Copy link
Member Author

rvagg commented Apr 29, 2015

sorry for the late notification @shigeki

@shigeki
Copy link
Contributor

shigeki commented Apr 29, 2015

@rvagg Never mind. I found this in the last minutes.

@mscdex mscdex added the meta Issues and PRs related to the general management of the project. label Apr 29, 2015
@silverwind
Copy link
Contributor

Added #1539 to the agenda (JS code style with two empty lines).

@Fishrock123
Copy link
Contributor

Adding #1559 unless it is otherwise cleared up beforehand

@domenic
Copy link
Contributor

domenic commented Apr 29, 2015

Do we really need to elevate decisions of style to the TC?

@silverwind
Copy link
Contributor

I suppose it's not strictly necessary. The other option would be to leave the PR pending for a week or so and merge if no one objects directly.

@Fishrock123
Copy link
Contributor

Not sure #1539 is worth discussing (yet?). I suppose we could talk about how much we'd be willing to re-style if we switched linters.. but I think the consensus will end up being "bare minimum" at most.

@silverwind
Copy link
Contributor

@Fishrock123 Agreed, let's give it a bit more time. There's a few more rules that will controversial because you can never satisfy everyone on style.

@trevnorris
Copy link
Contributor

@silverwind just to double check, will the style match to best possible what's already there or is it making drastic changes?

@silverwind
Copy link
Contributor

@trevnorris no real drastic changes except the double newline thing, which I think wasn't enforced by the old linter either.

Most of the changes are var redefinitions in the same scope and a few other inconistencies the old linter didn't catch. We'll try to keep the changes to a minimum.

@Rossolson
Copy link

Seems like the timezone dates didn't get changed:

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

@rvagg
Copy link
Member Author

rvagg commented May 13, 2015

sorry for the late notification @shigeki

@rvagg rvagg closed this as completed May 13, 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

8 participants