-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Nominating @psmarshall as a Collaborator #23849
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
meta
Issues and PRs related to the general management of the project.
Comments
+1 |
1 similar comment
+1 |
👍 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 (I forgot to do this after the collab summit... sorry 😞) |
+1 |
2 similar comments
+1 |
+1 |
+1 |
@psmarshall I'm available to onboard you at NCEU. |
@mcollina OK sounds good, thanks |
+1 |
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. |
This appears to be done! (Thanks to whoever handled the onboarding.) |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to nominate @psmarshall as a Collaborator. They are on the V8 team at Google and do a lot with benchmarks. They have eight commits on master but also a number of backports of V8 fixes and ABI compatibility patches for LTS versions so that V8 can be updated there.
Commits: https://github.com/nodejs/node/commits?author=psmarshall
Comments: https://github.com/nodejs/node/search?q=commenter%3Apsmarshall&type=Issues
Especially for the backports, being able to kick off the V8 CI jobs will be helpful for them.
@nodejs/collaborators
The text was updated successfully, but these errors were encountered: