-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 @shisama as a collaborator #23850
Labels
meta
Issues and PRs related to the general management of the project.
Comments
addaleax
added
the
meta
Issues and PRs related to the general management of the project.
label
Oct 24, 2018
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
joyeecheung
added
the
tsc-agenda
Issues and PRs to discuss during the meetings of the TSC.
label
Oct 31, 2018
This has been open for a week so according to the GOVERNANCE.md the nomination has now been considered accepted. Marking it as tsc-agenda so that it gets announced at the TSC meeting. |
Trott
removed
the
tsc-agenda
Issues and PRs to discuss during the meetings of the TSC.
label
Nov 5, 2018
targos
pushed a commit
that referenced
this issue
Nov 6, 2018
PR-URL: #24136 Fixes: #23850 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
kiyomizumia
pushed a commit
to kiyomizumia/node
that referenced
this issue
Nov 15, 2018
PR-URL: nodejs#24136 Fixes: nodejs#23850 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
codebytere
pushed a commit
that referenced
this issue
Nov 29, 2018
PR-URL: #24136 Fixes: #23850 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Nov 29, 2018
PR-URL: #24136 Fixes: #23850 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
MylesBorins
pushed a commit
that referenced
this issue
Dec 3, 2018
PR-URL: #24136 Fixes: #23850 Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Vse Mozhet Byt <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to nominate @shisama as a Collaborator. With 30 commits and consistent engagement in Node.js core, this should probably have happened a while ago :)
Commits: https://github.com/nodejs/node/commits?author=shisama
Comments: https://github.com/nodejs/node/search?q=commenter%3Ashisama&type=Issues
The text was updated successfully, but these errors were encountered: