Skip to content

offboard sam-github from build-wg #2339

Closed

Description

@sam-github

Hi folks. I'm not expecting to have time to work on the build going forward. @AshCripps and @richardlau are well able to continue anything I was working on. Its been a pleasure to help out where I could. If something comes up where some bit of information is missing that only I have (I really don't expect that), please don't hesitate to reach out to me, and I'll do my best.

I'll offboard myself to save you all the work :-)

Cheers!

Offboarding issue checklist

(Remove items if not applicable)

  • Remove their GPG key from test group in nodejs-private/secrets
  • Remove their GPG key from release group in nodejs-private/secrets
  • Remove their GPG key from infra group in nodejs-private/secrets
  • Remove their GPG key from infra-macstadium group in nodejs-private/secrets
  • Remove their GPG key from github-bot group in nodejs-private/secrets
  • Remove them from build teams they are a member of:
    • nodejs/build
    • nodejs/build-release
    • nodejs/build-infra
    • nodejs/jenkins-admins
    • nodejs/jenkins-release-admins
    • nodejs-private/build
  • PR changes to README.md to move the member to emeritus status
  • Run ncu team sync to vaildate the user has been removed from the build teams
  • Remove them from the nodejs/email alias

Activity

  1. richardlau commented on Jun 4, 2020

    @richardlau
    Member

    Thanks @sam-github for everything you’ve done.

  2. sam-github commented on Jun 4, 2020

    @sam-github
    ContributorAuthor

    Sorry, I can't remove my secret keys. That makes sense, dotgpg can't encrrypt the file with a key if that key isn't allowed to decrypt the file.

    I'll do the github stuff.

  3. richardlau commented on Jun 4, 2020

    @richardlau
    Member

    Sorry, I can't remove my secret keys. That makes sense, dotgpg can't encrrypt the file with a key if that key isn't allowed to decrypt the file.

    I'll do the github stuff.

    I’ll do this tomorrow if nobody else does first.

  4. sam-github commented on Jun 4, 2020

    @sam-github
    ContributorAuthor

    sigh.

    w/build (master u=) % ncu-team sync README.md
    ✔  Received member information of nodejs/build
    ✔  Received member information of nodejs/build-infra
    ✔  Received member information of nodejs/jenkins-admins
    ✔  Received member information of nodejs/jenkins-release-admins
    ✔  Received member information of nodejs/github-bot
    Error: ENOENT: no such file or directory, mkdir
        at Object.mkdirSync (fs.js:940:3)
        at exports.writeFile (/home/sam/.nvm/versions/node/v12.16.3/lib/node_modules/node-core-utils/lib/file.js:18:8)
        at Function.TeamInfo.syncFile (/home/sam/.nvm/versions/node/v12.16.3/lib/node_modules/node-core-utils/lib/team_info.js:61:3)
        at processTicksAndRejections (internal/process/task_queues.js:97:5)
        at async main (/home/sam/.nvm/versions/node/v12.16.3/lib/node_modules/node-core-utils/bin/ncu-team:64:7) {
      errno: -2,
      syscall: 'mkdir',
      code: 'ENOENT'
    }
    
  5. added a commit that references this issue on Jun 4, 2020
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