Skip to content

Nominating dario-piotrowicz as a collaborator #57983

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

Closed
jasnell opened this issue Apr 22, 2025 · 18 comments
Closed

Nominating dario-piotrowicz as a collaborator #57983

jasnell opened this issue Apr 22, 2025 · 18 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@jasnell
Copy link
Member

jasnell commented Apr 22, 2025

Dario is a colleague of myself and @anonrig at Cloudflare. They have been working with and have been onboarded onto the @nodejs/nodejs-website team and have been actively contributing to nodejs/node for the past few months. They would make a great candidate for node.js collaborator.

cc @nodejs/collaborators @nodejs/tsc @dario-piotrowicz

@avivkeller
Copy link
Member

Speaking as a member of @nodejs/nodejs-website, @dario-piotrowicz has been an amazing addition to our team, and we've all had a great experience working with them!

@RaisinTen
Copy link
Member

Definitely +1!

@UlisesGascon
Copy link
Member

Huge +1!

@marco-ippolito
Copy link
Member

+1

1 similar comment
@mcollina
Copy link
Member

+1

@mhdawson
Copy link
Member

+1 from me

@VoltrexKeyva VoltrexKeyva added the meta Issues and PRs related to the general management of the project. label Apr 23, 2025
@ovflowd
Copy link
Member

ovflowd commented Apr 23, 2025

I wish I could give a +1 but I'm not a collaborator anymore. But if I could, definitely a huge +1 <3

@juanarbol
Copy link
Member

+1 from me

@anonrig
Copy link
Member

anonrig commented Apr 30, 2025

It's been more than seven days, which means this nomination has passed, congrats! @dario-piotrowicz can you confirm publicly that you're interested? If so, let's schedule an onboarding.

@dario-piotrowicz
Copy link
Member

Hey @anonrig, thank you very much! 😄

Yes, I'm definitely interested! Let's schedule an onboarding 😄

Also I would really like to thank @jasnell a lot for the nomination and thanks a lot also for everyone's support and trust, I'm really looking forward to it and I'll do my very best to earn my place as collaborator 🫶

@anonrig
Copy link
Member

anonrig commented Apr 30, 2025

Happ to hear that! I'll schedule a call with @dario-piotrowicz.

@RaisinTen
Copy link
Member

#58102 has landed, so I'm closing this. Welcome Dario! :)

@dario-piotrowicz
Copy link
Member

Thanks @RaisinTen 😄 🫶

However I added Fixes https://github.com/nodejs/node/issues/57983 in #58102 so shouldn't this issue have been closed automatically? 🤔

@anonrig
Copy link
Member

anonrig commented May 2, 2025

It should have been?

@RaisinTen
Copy link
Member

The GitHub PR description does have the Fixes link but it was closed and the commit that landed on main c240c03 does not have the Fixes link, so that's why this didn't get auto-closed

@dario-piotrowicz
Copy link
Member

mh.... is this expected? or did I mess up the PR landing? 🤔 (the fixes link was definitely present in the PR description as we were going through the landing process)

@targos
Copy link
Member

targos commented May 2, 2025

We expect the "Fixes" line to be a valid commit trailer, so it should have a colon: Fixes: https://github.com... to be picked up by the git node land command.

@dario-piotrowicz
Copy link
Member

Ah ok I see, thanks a bunch for the clarification @targos 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging a pull request may close this issue.