Skip to content

Nominating Timothy Gu #485

Description

@Trott

@addaleax and others wish to nominate @TimothyGu to the TSC, so here's an issue to get that going.

Timothy, we'll invite you as a non-voting participant/observer for the next few meetings. If you think you are more likely to miss meetings than be able to attend due to scheduling conflicts or anything else, let's talk a bit. It might be time to re-evaluate the meeting times anyway. (I try to do it once a month, as that's about the cadence where we add someone and/or drop someone these days.)

Activity

  1. Trott commented on Feb 5, 2018

    @Trott
    MemberAuthor

    I guess it's traditional to leave a lengthy list of the person's accomplishments with the nomination. Timothy has been a huge help with newcomers, has done fantastic work on the WHATWG-URL stuff, is more into reading specs than most of us, has been involved in Code + Learn events, and has done a bunch more that I'm leaving out.

    Maybe instead of a parade of +1 comments, people can instead leave a comment listing something awesome Timothy did. :-D

  2. TimothyGu commented on Feb 6, 2018

    @TimothyGu
    Member

    I am honored to be nominated to the TSC! Excited to do what I can to help make Node.js a better project.

  3. added a commit that references this issue on Feb 8, 2018
  4. richardlau commented on Feb 8, 2018

    @richardlau
    Member

    I've opened a pull request against Michael's create-node-meeting-artifacts tool to add @TimothyGu as an observer to the TSC meetings.

  5. added a commit that references this issue on Feb 8, 2018
  6. fhinkel commented on Feb 9, 2018

    @fhinkel
    Contributor

    big +1 for fearlessly digging into V8 interceptors ❤️ Happy to have you on the TSC soon.

  7. TimothyGu commented on Mar 27, 2018

    @TimothyGu
    Member

    After the end of my last term last week, I should be able to make it to at least one time slot out of three (5pm, and possibly 2pm UTC) from the next week on.

  8. added a commit that references this issue on Apr 19, 2018
  9. added a commit that references this issue on Jul 27, 2026
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions