Skip to content

io.js TC Meeting 2014-12-10 #112

Description

@rvagg

This week:

  • Sydney (me): 7am 6am Thursday
  • Amsterdam: 9pm 8pm Wednesday
  • Moscow: 11pm 10pm Wednesday
  • San Francisco: 12 noon 11am Wednesday

All other timezones: http://www.timeanddate.com/worldclock/fixedtime.html?msg=io.js+TC+Meeting+2014-12-10&iso=20141211T07&p1=240&ah=1
http://www.timeanddate.com/worldclock/fixedtime.html?msg=io.js+TC+Meeting+2014-12-10&iso=20141211T06&p1=240&ah=1

(Note: moved 1 hour earlier for @indutny)

Public YouTube feed: http://www.youtube.com/watch?v=otE4IRMVUMo

Invited: @bnoordhuis @piscisaureus @indutny @isaacs @TooTallNate @trevnorris

Clash with JSFest so @mikeal won't be present.

Agenda and minutes doc, editable by TC, commentable by everyone else: https://docs.google.com/document/d/1hTgqljZeRf29COYz-CsjlkT-vFcAtj-jxvm3KjKPam8/edit (written in markdown so we can put it straight into the repo)

Agenda so far:

Activity

  1. algesten commented on Dec 8, 2014

    @algesten

    this bot is not at all annoying... :)

  2. rvagg commented on Dec 8, 2014

    @rvagg
    MemberAuthor

    alternative

  3. indutny commented on Dec 8, 2014

    @indutny
    Member

    @rvagg sounds good

  4. indutny commented on Dec 8, 2014

    @indutny
    Member

    Oh wait, it doesn't sound good at all. I'll be in a different TZ at the moment, +4 hours from Moscow.

  5. rvagg commented on Dec 8, 2014

    @rvagg
    MemberAuthor

    @indutny are you too weak for a 3am call?

    care to propose a different day or time? my schedule is filling up this week but I don't have much going on in the 7am range

  6. indutny commented on Dec 8, 2014

    @indutny
    Member

    @rvagg you better tell @caineio that this is about v0.12 and docs. :)

    @rvagg ok, let's aim for 3am. If I'll be too weak - I'll just read the notes afterwards :)

  7. piscisaureus commented on Dec 8, 2014

    @piscisaureus
    Contributor

    I got a cough strong feeling that the @chrisdickinson nomination is uncontroversial.
    Is there any reason not to invite him too?

  8. rvagg commented on Dec 8, 2014

    @rvagg
    MemberAuthor

    good point, I'll make sure he gets the link too

  9. added
    docIssues and PRs related to Node.js documentation.
    and removed on Dec 8, 2014
  10. rvagg commented on Dec 8, 2014

    @rvagg
    MemberAuthor

    Moved one hour forward to accommodate @indutny:

    • Sydney (me): 6am Thursday
    • Amsterdam: 8pm Wednesday
    • Moscow: 10pm Wednesday
    • San Francisco: 11am Wednesday

    All other timezones: http://www.timeanddate.com/worldclock/fixedtime.html?msg=io.js+TC+Meeting+2014-12-10&iso=20141211T06&p1=240&ah=1

  11. 23 remaining items

  12. Fishrock123 commented on Dec 10, 2014

    @Fishrock123
    Contributor

    Could you guys edit the post to use WolframAlpha for date/time? It's more accurate and easier to read http://www.wolframalpha.com/input/?i=7pm+GMT+Wednesday%2C+December+10%2C+2014+in+local+time

  13. rvagg commented on Dec 10, 2014

    @rvagg
    MemberAuthor
  14. rvagg commented on Dec 10, 2014

    @rvagg
    MemberAuthor

    @Fishrock123 will try and remember that for next time, I need to document the procedure for today's meeting because I think it worked quite well and we had a lot of engagement on the various channels

  15. jbergstroem commented on Dec 10, 2014

    @jbergstroem
    Member

    @rvagg Just wanted to say I appreciate the super-quick turnaround for uploading (and even publishing) the meeting. It's a great way for consumers like me to feel part of the community.

  16. micnic commented on Dec 10, 2014

    @micnic
    Contributor

    @jbergstroem +1, @rvagg thanks a lot for keeping us up to date with the meeting you had !

  17. cjihrig commented on Dec 10, 2014

    @cjihrig
    Contributor

    Are the links going to be documented anywhere, or just live on the relevant issue?

  18. rvagg commented on Dec 10, 2014

    @rvagg
    MemberAuthor

    will put it in the doc and put in a PR very soon, working on it right now

  19. rlidwka commented on Dec 10, 2014

    @rlidwka
    Contributor

    Could you guys edit the post to use WolframAlpha for date/time? It's more accurate and easier to read

    How about using UTC for all date/time values?

  20. added a commit that references this issue on Dec 12, 2014
    41ec1a7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions