Skip to content
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 Joe Sepi (@joesepi) as collaborator #41671

Closed
mmarchini opened this issue Jan 24, 2022 · 7 comments
Closed

Nominating Joe Sepi (@joesepi) as collaborator #41671

mmarchini opened this issue Jan 24, 2022 · 7 comments
Labels
feature request Issues that request new features to be added to Node.js.

Comments

@mmarchini
Copy link
Contributor

What is the problem this feature will solve?

Joe Sepi is not collaborator

What is the feature you are proposing to solve the problem?

Joe Sepi as collaborator

What alternatives have you considered?


I'd like to nominate Joe Sepi (@joesepi) to be a collaborator. He has been an active and trustworthy member of the wider Node.js project for years, and is currently one of the project representatives at the OpenJS Cross Project Council. While he hasn't made many code contributions to nodejs/node, he brings a positive impact to the project as a whole. Furthermore, he recently demonstrated interest in volunteering to help with security releases, a role that is considerably easier for those with commit access.

@mmarchini mmarchini added the feature request Issues that request new features to be added to Node.js. label Jan 24, 2022
@mhdawson
Copy link
Member

+1 from me.

@iansu
Copy link
Contributor

iansu commented Jan 24, 2022

+1

1 similar comment
@benjamingr
Copy link
Member

+1

@benjamingr
Copy link
Member

@mmarchini off topic: @targos showed me last week you can bypass templates by appending /new to /issues ( https://github.com/nodejs/node/issues/new )

@bcoe
Copy link
Contributor

bcoe commented Jan 25, 2022

+1, @joesepi has been a significant contributor to the tooling meetings.

@mhdawson
Copy link
Member

mhdawson commented Feb 4, 2022

As per our governance this is now approved as there have been no objections for over a week. @joesepi welcome as a collaborator.

I'll volunteer to onboard Joe unless somebody else wants to do it. Anybody else want to join me?

@DerekNonGeneric
Copy link
Contributor

Congrats @joesepi!

Anybody else want to join me?

I want to join the onboarding call; let me know when the onboarding session is, I can probably fit that into my calendar next week.

joesepi added a commit that referenced this issue Feb 9, 2022
@joesepi joesepi closed this as completed in 255554e Feb 9, 2022
bengl pushed a commit to bengl/node that referenced this issue Feb 21, 2022
Fixes: nodejs#41671

PR-URL: nodejs#41914
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
bengl pushed a commit to bengl/node that referenced this issue Feb 21, 2022
Fixes: nodejs#41671

PR-URL: nodejs#41914
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
danielleadams pushed a commit to danielleadams/node that referenced this issue Apr 21, 2022
Fixes: nodejs#41671

PR-URL: nodejs#41914
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Beth Griggs <bgriggs@redhat.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issues that request new features to be added to Node.js.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants