Skip to content

Nominating Sam Roberts (@sam-github) to the TSC #687

Closed

Description

@rvagg

No objections from the TSC so far and Sam has given a 👍 so I'm nominating him for the TSC. The case for Sam on the TSC is that (a) he has a long history with Node core and that kind of perspective aids in continuity and stability and (b) he's essentially taking over leadership of crypto, or OpenSSL at least, an area where the TSC could do with more representation (I've been phasing out of that area and Sam has been picking up the reigns and I think he's a much better fit than me anyway!). I also expect that Sam is the most likely person to be handling many of the security releases in the near future and having an additional level of authority to get all of the awkward things done and being able to take responsibility for difficult decisions is helpful for that.

Activity

  1. sam-github commented on Apr 4, 2019

    @sam-github
    Contributor

    Thanks for the nomination, you all, I am looking forward to doing what I can to help the TSC.

  2. mhdawson commented on Apr 4, 2019

    @mhdawson
    Member

    I'll open a PR tomorrow to add @sam-github to the observer list for the next TSC meetings.

  3. rvagg commented on Apr 29, 2019

    @rvagg
    MemberAuthor

    I can't remember what the procedure with this is, is it 3 weeks observer then 4th week vote? @sam-github how many weeks has it been since you got to be an observer?

  4. Trott commented on Apr 29, 2019

    @Trott
    Member

    I can't remember what the procedure with this is, is it 3 weeks observer then 4th week vote? @sam-github how many weeks has it been since you got to be an observer?

    It's been 3 the last few times. It used to be 4 but that seemed a bit longer than necessary to me.

  5. sam-github commented on Apr 29, 2019

    @sam-github
    Contributor

    @rvagg There have been 3 TSC meetings since I was added as an observer, I was present at the last 2 (the first was too early in my TZ).

  6. rvagg commented on Apr 30, 2019

    @rvagg
    MemberAuthor

    Adding on agenda for whenever the next meeting happens, votes can be collected in here if you're not attending. A +1 from me obviously (next week's meeting is 2am for me and this week looks like it's being cancelled and is not a great time anyway).

  7. Trott commented on Apr 30, 2019

    @Trott
    Member

    +1

  8. gireeshpunathil commented on Apr 30, 2019

    @gireeshpunathil
    Member

    +1

  9. danbev commented on Apr 30, 2019

    @danbev
    Contributor

    +1

  10. targos commented on Apr 30, 2019

    @targos
    Member

    +1

  11. cjihrig commented on Apr 30, 2019

    @cjihrig
    Contributor

    +1

  12. ChALkeR commented on Apr 30, 2019

    @ChALkeR
    Member

    +1

  13. 1 remaining item

  14. mcollina commented on May 8, 2019

    @mcollina
    SponsorMember

    +1

  15. mhdawson commented on May 8, 2019

    @mhdawson
    Member

    +1

  16. rvagg commented on May 8, 2019

    @rvagg
    MemberAuthor

    12 of 18 have either provided a +1 or a 👍, no negatives (that I'm aware of). This week's meeting might be cancelled, #700, so I'm going call this successful and welcome @sam-github on board.

    I'll open a PR to the README in nodejs/node, when that's merged we can do the other permissiony things that need to be done.

    Before that lands, there is still time if there are any remaining concerns among TSC members. Please voice them now or contact me, or someone else on the TSC that you trust that can make it actionable.

  17. rvagg commented on May 8, 2019

    @rvagg
    MemberAuthor
  18. gabrielschulhof commented on May 8, 2019

    @gabrielschulhof

    +1

  19. added a commit that references this issue on May 9, 2019
  20. added a commit that references this issue on May 9, 2019
  21. added a commit that references this issue on May 9, 2019
  22. added a commit that references this issue on Jul 16, 2024
  23. added a commit that references this issue on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions