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 bcoe as a collaborator #20242

Closed
MylesBorins opened this issue Apr 24, 2018 · 26 comments
Closed

Nominating bcoe as a collaborator #20242

MylesBorins opened this issue Apr 24, 2018 · 26 comments

Comments

@MylesBorins
Copy link
Contributor

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

@devsnek
Copy link
Member

devsnek commented Apr 24, 2018

with all due respect to the nominee, it seems like they haven't been active with core since oct/nov 2017?

@bcoe
Copy link
Contributor

bcoe commented Apr 24, 2018

👋 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.

@gireeshpunathil
Copy link
Member

+1

@TimothyGu
Copy link
Member

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 😀

@apapirovski
Copy link
Contributor

+1 here

@ofrobots
Copy link
Contributor

+1.

@trivikr
Copy link
Member

trivikr commented Apr 26, 2018

+1

3 similar comments
@benjamingr
Copy link
Member

+1

@targos
Copy link
Member

targos commented Apr 26, 2018

+1

@maclover7
Copy link
Contributor

+1

@MylesBorins MylesBorins added tsc-review tsc-agenda Issues and PRs to discuss during the meetings of the TSC. and removed tsc-review labels May 3, 2018
@MylesBorins
Copy link
Contributor Author

Seems like we have a bunch of plus ones, putting it on tsc-agenda

@refack
Copy link
Contributor

refack commented May 3, 2018

a belated +1

@jasnell
Copy link
Member

jasnell commented May 8, 2018

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.

@fhinkel fhinkel removed the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label May 8, 2018
@mhdawson
Copy link
Member

mhdawson commented May 9, 2018

+1

1 similar comment
@danbev
Copy link
Contributor

danbev commented May 9, 2018

+1

@TimothyGu
Copy link
Member

It seems like @bcoe has started to become more active recently: #20391. I am now +1 on moving forward with the nomination.

@ChALkeR
Copy link
Member

ChALkeR commented May 9, 2018

+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.

@fhinkel fhinkel added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label May 28, 2018
@Trott Trott removed the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jun 2, 2018
@MylesBorins MylesBorins added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jun 13, 2018
@MylesBorins
Copy link
Contributor Author

this was announced at the TSC meeting today and is ready to move forward.

@nodejs/onboarding anyone able to get ben onboarded?

@MylesBorins MylesBorins removed the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jun 13, 2018
@fhinkel
Copy link
Member

fhinkel commented Jun 13, 2018

Welcome @bcoe. Happy to have you as a collaborator!

@bcoe
Copy link
Contributor

bcoe commented Jun 14, 2018

thank you so much 🎉 I'm looking very much forward to my continued work on the Node.js project, especially the mentorship program.

@MylesBorins
Copy link
Contributor Author

ping @nodejs/onboarding

@Trott
Copy link
Member

Trott commented Jun 21, 2018

@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).

@bcoe
Copy link
Contributor

bcoe commented Jun 22, 2018

@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.

@Trott
Copy link
Member

Trott commented Jun 23, 2018

@bcoe I'll send you an email.

@MylesBorins
Copy link
Contributor Author

They have been onboarded, thank you

@benjamingr
Copy link
Member

Welcome @bcoe !!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests