Visitar URL original
Nominating @anonrig to the TSC · Issue #1411 · nodejs/TSC · GitHub
Skip to content

Nominating @anonrig to the TSC #1411

Closed
Closed

Description

@mcollina

Yagiz brought back a focus on performance that was lost to Node.js. After many PRs and contributions that slightly improved the performance of Node.js, he helped forming a new team that was dedicated to that task. After months of work, Yagiz also contributed a new URL implementation, solving a problematic bottleneck for many use cases.

It is my privilege to nominate Yagiz to the Node.js TSC.

Activity

  1. mhdawson commented on Jul 5, 2023

    @mhdawson
    Member

    +1 from me.

  2. Trott commented on Jul 14, 2023

    @Trott
    Member

    @nodejs/tsc

  3. Trott commented on Jul 14, 2023

    @Trott
    Member

    Added to TSC agenda so that we can get resolution and move forward. Hopefully we get resolution and move forward before the meeting.

  4. RafaelGSS commented on Jul 14, 2023

    @RafaelGSS
    Member

    I think both nominations were mentioned in the 2 previous TSC sessions. I think we can just move forward at this point.

  5. mhdawson commented on Jul 19, 2023

    @mhdawson
    Member

    Starting on the onboarding

    • Confirm that the new member has read, understands, and agrees to uphold the
      Code of Conduct.
    • Add the new member to the @nodejs/tsc and @nodejs/security-tsc teams.
    • Change the new member's role in the GitHub nodejs organization to Owner.
    • Add them to the @nodejs-private org and with an Owner role.
    • Add them to the @nodejs-private/security-tsc team.
    • Add them to the @pkgjs org and with an Owner role.
    • Add them to the @pkgjs/node-tsc team.
    • Invite them to the HackerOne Node.js team.
      Have them turn on two- factor authentication after they have joined.
    • Add them to the tsc and crypto-export mailing lists. - Add new TSC members email#225
    • Add them to the nodejs-tsc Google Group as owners, so they receive Calendar invites for TSC meetings.
    • Update the @nodejs/node repository README to reflect membership in the TSC. -doc: add new TSC members node#48841
    • Update https://github.com/nodejs/create-node-meeting-artifacts/blob/main/templates/invited_tsc to reflect membership in the TSC.
    • Inform them of the TSC meeting password.
    • Ask them what is their handle on OpenJS Slack – and ask them to create one if they haven't one already. Add that handle to the #nodejs-tsc channel.

    @anonrig can you confirm that the new member has read, understands, and agrees to uphold the Code of Conduct.

  6. added a commit that references this issue on Jul 19, 2023
  7. anonrig commented on Jul 19, 2023

    @anonrig
    Member

    I've read, understood and agree to uphold Node.js's code of conduct. Thank you for the nomination and for this responsibility.

  8. mhdawson commented on Jul 19, 2023

    @mhdawson
    Member

    @anonrig let me know once you have accepted the HackerOne invitation and have turned on 2FA

  9. mhdawson commented on Jul 20, 2023

    @mhdawson
    Member

    Onboarding complete. @anonrig welcome !

  10. added a commit that references this issue on Aug 14, 2023
  11. added a commit that references this issue on Aug 15, 2023
  12. added a commit that references this issue on Nov 27, 2023
  13. added a commit that references this issue on Jul 16, 2024
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