-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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 @abmusse to be a collaborator #54733
Comments
CC @abmusse (I'm not sure if @-ing a user in the title will actually ping them) |
I see I missed at mentioning all collaborators as per - Line 169 in 1d2603b
@nodejs/collaborators |
Ok I think we can consider this approved as its been open for over a week with a numbers of +1s and no objections. @abmusse congratulations! |
I'll volunteer to onboard @abmusse anybody else want to join to help withe onboarding? |
@abmusse lets sync up to set up an time for onboarding. |
We've scheduled the onboarding for Sep 23rd at 2 ET if anybody else want's to join. |
Abdirahim has been working to keep Node.js running/passing tests on IBMi and regularly checks the CI for failures and investigates/resolves issues. They are also a build WG member helping maintain IBMi and other machines. They have also been active in libuv helping with IBMi and AIX related issues - https://github.com/search?q=repo%3Alibuv%2Flibuv+author%3Aabmusse
Being able to run the CI would be helpful and I think they have enough commits and involvement in the Node.js repos to warrant a collaborator nomination.
Commits authored on nodejs/node: github.com/nodejs/node/commits?author=abmusse
Pull requests opened: github.com/search?q=author:abmusse+org:nodejs&type=pullrequests
Issues opened: github.com/search?q=author:abmusse+org:nodejs&type=issues
Comments on pull requests and issues throughout the Node.js organization: https://github.com/search?q=commenter%3Aabmusse+org%3Anodejs&type=pullrequests
The text was updated successfully, but these errors were encountered: