Skip to content

Nominating bcoe as a collaborator #20242

Closed

Description

@MylesBorins

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

Activity

  1. devsnek commented on Apr 24, 2018

    @devsnek
    Member

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

  2. bcoe commented on Apr 24, 2018

    @bcoe
    Contributor

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

  3. gireeshpunathil commented on Apr 24, 2018

    @gireeshpunathil
    Member

    +1

  4. TimothyGu commented on Apr 24, 2018

    @TimothyGu
    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 😀

  5. apapirovski commented on Apr 26, 2018

    @apapirovski
    Contributor

    +1 here

  6. ofrobots commented on Apr 26, 2018

    @ofrobots
    Contributor

    +1.

  7. trivikr commented on Apr 26, 2018

    @trivikr
    Member

    +1

  8. benjamingr commented on Apr 26, 2018

    @benjamingr
    Member

    +1

  9. targos commented on Apr 26, 2018

    @targos
    Member

    +1

  10. maclover7 commented on Apr 27, 2018

    @maclover7
    Contributor

    +1

  11. added
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    and removed on May 3, 2018
  12. MylesBorins commented on May 3, 2018

    @MylesBorins
    ContributorAuthor

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

  13. refack commented on May 3, 2018

    @refack
    Contributor

    a belated +1

  14. 5 remaining items

  15. ChALkeR commented on May 9, 2018

    @ChALkeR
    Member

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

  16. added
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    on May 28, 2018
  17. removed
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    on Jun 2, 2018
  18. added
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    on Jun 13, 2018
  19. MylesBorins commented on Jun 13, 2018

    @MylesBorins
    ContributorAuthor

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

    @nodejs/onboarding anyone able to get ben onboarded?

  20. removed
    tsc-agendaIssues and PRs to discuss during Technical Steering Committee meetings.
    on Jun 13, 2018
  21. fhinkel commented on Jun 13, 2018

    @fhinkel
    Contributor

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

  22. bcoe commented on Jun 14, 2018

    @bcoe
    Contributor

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

  23. MylesBorins commented on Jun 21, 2018

    @MylesBorins
    ContributorAuthor

    ping @nodejs/onboarding

  24. Trott commented on Jun 21, 2018

    @Trott
    Member

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

  25. bcoe commented on Jun 22, 2018

    @bcoe
    Contributor

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

  26. Trott commented on Jun 23, 2018

    @Trott
    Member

    @bcoe I'll send you an email.

  27. MylesBorins commented on Jun 27, 2018

    @MylesBorins
    ContributorAuthor

    They have been onboarded, thank you

  28. benjamingr commented on Jun 27, 2018

    @benjamingr
    Member

    Welcome @bcoe !!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions