-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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 Shigeki Ohtsu @shigeki to the TC #1501
Labels
meta
Issues and PRs related to the general management of the project.
Comments
Thanks for the nomination. It's a great honor for me to join TC. The timezone issue is common to all members so I will do my best to make it up as much as I can. |
🎉 🎉 🎉 |
Well deserved! Congrats, @shigeki! |
Fishrock123
added
the
meta
Issues and PRs related to the general management of the project.
label
Apr 22, 2015
rvagg
added a commit
to rvagg/io.js
that referenced
this issue
Jun 23, 2015
voted in to Node.js Foundation TSC in meeting on 2015-06-17 Closes: nodejs#1500 Closes: nodejs#1501 PR-URL: nodejs#2008 Reviewed-By: Ben Noordhuis <[email protected]>
done, @shigeki is now a TSC member |
Congrats @shigeki :-) |
mscdex
pushed a commit
to mscdex/io.js
that referenced
this issue
Jul 9, 2015
voted in to Node.js Foundation TSC in meeting on 2015-06-17 Closes: nodejs#1500 Closes: nodejs#1501 PR-URL: nodejs#2008 Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Shigeki has agreed to this nomination and has been invited to participate in the io.js TC meetings for a few weeks in a non-voting capacity.
Shigeki has quickly become of the most active contributors to io.js and has been instrumental in maintaining OpenSSL support, including the major (but smooth!) upgrade to v1.0.2. He'll also be the first representative on the TC from Asia, specifically Japan where there is a very active Node/io.js community so he adds some more geographic diversity to the group.
One note about @shigeki's addition is that he's in UTC+9, which means we now span so many timezones that there's unlikely to be a comfortable overlap for meetings (it's already a stretch). So we'll likely need to figure out new strategies for meetings in the future.
The text was updated successfully, but these errors were encountered: