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

Nominating Timothy Gu #485

Closed
Trott opened this issue Feb 5, 2018 · 5 comments
Closed

Nominating Timothy Gu #485

Trott opened this issue Feb 5, 2018 · 5 comments

Comments

@Trott
Copy link
Member

Trott commented Feb 5, 2018

@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.)

@Trott
Copy link
Member Author

Trott commented Feb 5, 2018

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

@TimothyGu
Copy link
Member

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

richardlau added a commit to richardlau/create-node-meeting-artifacts that referenced this issue Feb 8, 2018
@richardlau
Copy link
Member

richardlau commented Feb 8, 2018

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

mhdawson pushed a commit to nodejs/create-node-meeting-artifacts that referenced this issue Feb 8, 2018
@fhinkel
Copy link
Member

fhinkel commented Feb 9, 2018

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

@TimothyGu
Copy link
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.

TimothyGu added a commit to TimothyGu/node that referenced this issue Apr 18, 2018
jasnell pushed a commit to nodejs/node that referenced this issue Apr 19, 2018
PR-URL: #20132
Fixes: nodejs/TSC#485
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ujjwal Sharma <usharma1998@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants