-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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 bcoe as a collaborator #20242
Comments
with all due respect to the nominee, it seems like they haven't been active with core since oct/nov 2017? |
👋 thank you for the nomination @MylesBorins. @devsnek during this period I've been putting work into nyc which is used as part of Node's unit testing suite, and have also been working on several libraries related to native test coverage in v8 -- my hope being that I'll be able to integrate this with Node's test suite over time. My wife passed away in January, which is a big part of why my open-source contributions go off a cliff for a couple months. I'm just starting to ramp back up on my open-source projects and hope to be quite active in Node.js throughout 2018. |
+1 |
I've very much enjoyed working with @bcoe on c8, and I think he would be a great addition to the project as a Collaborator. As he said, he plans on being more active this year in open source, and I don't think it would be too late to formally welcome him into the project at that time, when he's ready to make more contributions 😀 |
+1 here |
+1. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Seems like we have a bunch of plus ones, putting it on tsc-agenda |
a belated +1 |
I'm generally +1 but would like to see a few PRs before we actually go through the onboarding. @bcoe ... my condolences on the loss of your wife. |
+1 |
1 similar comment
+1 |
+1 to this. On the meta side: the concern @devsnek expressed above is valid and on-topic, and I am rather disappointed to see it receiving mostly downwotes. I would rather see more people expressing opinions like that openly in the future. The downvote thing is likely caused by a problem with reactions on the GitHub side, though, which I'm constantly whining about. |
this was announced at the TSC meeting today and is ready to move forward. @nodejs/onboarding anyone able to get ben onboarded? |
Welcome @bcoe. Happy to have you as a collaborator! |
thank you so much 🎉 I'm looking very much forward to my continued work on the Node.js project, especially the mentorship program. |
ping @nodejs/onboarding |
@MylesBorins Any TSC member can do the onboarding, so you can do it yourself if you are so inclined (and have the time, of course). |
@Trott @addaleax @MylesBorins @TimothyGu I can work around your schedules, just let me know a time that works in the next week ... I'm excited. |
@bcoe I'll send you an email. |
They have been onboarded, thank you |
Welcome @bcoe !!! |
Hey All,
I'd like to nominate @bcoe to be a collaborator. They have been a long time contributor to the nodejs ecosystem and would make a find addition to the team:
Commits in the nodejs/node repository.
Pull requests and issues opened in the nodejs/node repository.
Comments and reviews on issues and pull requests in the nodejs/node repository
The text was updated successfully, but these errors were encountered: