Sitelet https://github.com/nodejs/node/issues/1502
Skip to content

io.js TC Meeting 2015-04-22 #1502

Description

@rvagg

UTC Wed 22-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

Note this time has shifted forward by one hour UTC from previous meetings

Or in your local time:

Please allow time for cat-herding before broadcast starts.

Public YouTube feed: http://www.youtube.com/watch?v=s7LIMsTFaps
Google Plus Event page: https://plus.google.com/events/co7i7pv2a51270jat7jvkfcue64
Google Doc for minutes: https://docs.google.com/document/d/1G4aJ2OwiW2WphW7Vz2OW56VRot8xRBFitluKsuYPxk0 (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 (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.

The first few of these are duplicates from the last meeting but I think they might still be relevant.

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

Activity

  1. added
    metaIssues and PRs related to the general management of the project.
    on Apr 22, 2015
  2. Fishrock123 commented on Apr 22, 2015

    @Fishrock123
    Contributor

    Can we do the TC nominations first, to get them out of the way?

  3. mikeal commented on Apr 22, 2015

    @mikeal
    Contributor

    Just as a point of process, I don't think we've got 24 hours on the latest nominations for @mscdex and @shigeki so, if there are objections, we'll need to a defer a vote until the next meeting.

  4. chrisdickinson commented on Apr 22, 2015

    @chrisdickinson
    Contributor

    If it's possible I'd like to update everyone on the results of the v1.8.0 release, and what I'd like to do for the upcoming v2.0.0 release.

  5. Fishrock123 commented on Apr 22, 2015

    @Fishrock123
    Contributor

    @chrisdickinson Please do. I suspect the "Ready to upgrade to V8 4.2?" will be about that in part.

  6. rvagg commented on Apr 22, 2015

    @rvagg
    MemberAuthor

    Sorry, I didn't mean for them to be voted on at this meeting, I just included them to explain why they are there. The suggestion was that they would join the TC meetings for a few weeks like @Fishrock123 did and then we vote at a later meeting.

  7. added a commit that references this issue on Apr 23, 2015
  8. Fishrock123 commented on Apr 23, 2015

    @Fishrock123
    Contributor

    @shigeki by the way, how did you find understanding the meeting? Was our english we clear enough?

  9. shigeki commented on Apr 23, 2015

    @shigeki
    Contributor

    @Fishrock123 Thanks for taking care of me. Everyone speaks very clear. But sometime I could not follow conversations because of my lack of understanding of agenda. It was very helpful for me that Rod takes notes simultaneously during the meeting. I'm sure I can catch up by reading minutes later.

  10. Fishrock123 commented on Apr 23, 2015

    @Fishrock123
    Contributor

    @shigeki Honestly I also had some trouble following today too, the agenda was a little back-and-forth. No worries. :)

  11. added a commit that references this issue on Apr 23, 2015
  12. rvagg commented on Apr 24, 2015

    @rvagg
    MemberAuthor

    @Fishrock123 how can we improve on the back-and-forth that you're seeing?

  13. Fishrock123 commented on Apr 24, 2015

    @Fishrock123
    Contributor

    how can we improve on the back-and-forth that you're seeing?

    Was mostly just this meeting, but we jumped ahead or something at some point after the TC nominations and I got lost in the schedule when trying to take notes. Was generally like "wait where are we at?" a couple times.

  14. rvagg commented on Apr 25, 2015

    @rvagg
    MemberAuthor

    "wait where are we at?"

    Whenever I'm in a meeting and am feeling like that then I like to call for some clarification or a back-up to figure it out. Anyone in these meetings should feel free to ask for a temporary halt if anything's unclear so we can make sure we proceed with everyone on the same page. This goes particularly for anyone trying to take notes!

  15. added a commit that references this issue on May 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    metaIssues and PRs related to the general management of the project.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions