Jordan Harband onboarding

还没有人认领这个 Issue。

从检查清单开始，核实 Node.js 组织、服务器、README.md、发布暂存分支、nodejs/docker-node 的 node.keys、通过 ./cli.sh add 操作的 nodejs/release-keys，以及通过 ncu-team sync README.md 操作的 nodejs/Release 中所要求的访问权限和密钥变更。完成意味着检查清单中的每一项都已完成，包括添加到 OpenJS Slack 团队。

由索引模型根据 Issue 内容生成。

Be added to the GitHub releasers team in the Node.js org (grants ci-release access)
Be added to the GitHub security-release team in the Node.js and nodejs-private orgs
Have a single, high quality SSH key added to the "dist" user on the primary www server (see below for guidelines regarding SSH key quality)
Open a PR to add their GPG key to the nodejs/node README.md
- Once landed, the key should be cherry-picked to all active release staging branches (i.e. the active vMM.x-staging branches).
- Any future updates to the key should also be cherry-picked to all active release staging branches.
Open a PR in nodejs/docker-node to add their GPG key to node.keys
Open a PR in nodejs/release-keys to add their GPG key via ./cli.sh add $KEY_ID:
Open a PR in nodejs/Release to add themself under the "Releasers team" heading via ncu-team sync README.md.
Add them to the #nodejs-release-private team on the OpenJS Slack.

cc: @ljharb

评估

调研方向

描述

贡献指南

从这里开始

nodejs/Release 的其他 Issue

相似的 Issue