-
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 @ljharb to be a Collaborator #55918
Comments
+1 |
Looks like we forgot to mention @nodejs/collaborators as our governance document stipulates Lines 169 to 170 in bc39796
|
+1 |
+1 I've had exclusively positive experiences in the past years. |
+1 I think that is a great addition! I've participated in WGs and spaces and I learned a lot from him. |
+1 |
+1 from me. @ljharb has been a generally positive influence in the interactions we have had. 🙂 |
+1 |
+1, he would be an awesome addition. |
+1 |
+1 - working with Jordan is great 😄 |
If I'm not mistaken, this has been open for more than a week with no objections so the nomination is officially successful. I believe the next step is for a TSC member to schedule an onboarding for Jordan. 🚀 |
I nominate @ljharb as a collaborator. He has been helping review code in Node.js for a long time and has expressed interest in becoming a releaser in the future. He is also an OpenJS Board member (https://openjsf.org/governance).
Commits authored on nodejs/node: github.com/nodejs/node/commits?author=ljharb
Pull requests opened: github.com/search?q=author:ljharb+org:nodejs&type=pullrequests
Issues opened: github.com/search?q=author:ljharb+org:nodejs&type=issues
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=commenter%3Aljharb+org%3Anodejs&type=pullrequests
The text was updated successfully, but these errors were encountered: