Repository navigation
io.js TC Meeting 2015-04-29 #1557
Description
Activity
Added #1539 to the agenda (JS code style with two empty lines).Adding #1559 unless it is otherwise cleared up beforehand
Do we really need to elevate decisions of style to the TC?
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.
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.
@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.
@silverwind just to double check, will the style match to best possible what's already there or is it making drastic changes?
@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
varredefinitions 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.Seems like the timezone dates didn't get changed:
- San Francisco: Wed
22-Mar-1513:00 - Amsterdam: Wed
22-Mar-1522:00 - Moscow: Wed
22-Mar-1523:00 - Sydney: Thu
23-Mar-1506:00
- San Francisco: Wed
UTC Wed 29-Apr-15 20: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.
Note: There will be time at the end of the meeting for interactive QA with people in the #io.js channel on Freenode.