现有的维护者和项目领导使用本指南来邀请和接纳新的维护者和项目领导。 普通 Homebrew 用户可能会觉得它很有趣,但这里没有用户需要了解的内容。
有人一直为 Homebrew 做出持续的高质量贡献,并且表现出能够做出比仅仅更新配方等更高级的贡献?我们邀请他们成为维护者吧!
首先,给他们发送邀请电子邮件
The Homebrew team and I really appreciate your help on issues, pull requests and
your contributions to Homebrew.
We would like to invite you to have commit access and be a Homebrew maintainer.
If you agree to be a maintainer, you should spend the majority of the time you
are working on Homebrew (in descending order of priority):
- reviewing pull requests (from users and other maintainers)
- triaging, debugging and fixing user-reported issues and applying
- opening PRs for widely used changes (e.g. version updates)
You should also be making contributions to Homebrew at least once per quarter.
You should watch or regularly check Homebrew/brew and/or Homebrew/homebrew-core
and/or Homebrew/homebrew-cask. Let us know which so we can grant you commit
access appropriately.
If you're no longer able to perform all of these tasks, please continue to
contribute to Homebrew, but we will ask you to step down as a maintainer.
A few requests:
- Please make pull requests for any changes in the Homebrew repositories (instead
of committing directly) and don't merge them unless you get at least one approval
and passing tests.
- Please review the Maintainer Guidelines at https://docs.brew.sh.cn/Maintainer-Guidelines
- Please review the team-specific guides for whichever teams you will be a part of.
Here are links to these guides:
- Homebrew/brew: https://docs.brew.sh.cn/Homebrew-brew-Maintainer-Guide
- Homebrew/homebrew-core: https://docs.brew.sh.cn/Homebrew-homebrew-core-Maintainer-Guide
- Homebrew/homebrew-cask: https://docs.brew.sh.cn/Homebrew-homebrew-cask-Maintainer-Guide
- Create branches in the main repository rather than on your fork to ease collaboration
with other maintainers and allow security assumptions to be made based on GitHub access.
- If still in doubt please ask for help and we'll help you out.
- Please read:
- https://docs.brew.sh.cn/Maintainer-Guidelines
- the team-specific guides linked above and in the maintainer guidelines
- anything else you haven't read on https://docs.brew.sh.cn
How does that sound?
Thanks for all your work so far!
如果他们接受,请按照以下几个步骤进行设置
machomebrew
私人 Slack(并确保他们已阅读 通信指南),并要求他们在那里使用他们的真实姓名(而不是他们在 GitHub 等平台上使用的化名)。如果出现问题,请要求他们辞去维护者的职务。
当他们因任何原因不再担任维护者时,撤销他们对上述所有内容的访问权限。
为了松散地验证维护者的身份并建立友谊,如果你发现自己与另一位 Homebrew 维护者在同一个城镇(例如居住、访问或参加会议),你应该努力与他们会面。如果你这样做,你可以 报销你的餐费(在 Homebrew 的可报销费用政策 范围内)。这是一个更轻松的版本,类似于其他项目使用的政策,例如 Debian 系统,以亲自会面来使用法律身份验证签署密钥。
现在坐下来,放松一下,让新维护者处理我们更多的贡献。
如果维护者或成员当选为 Homebrew 的 项目领导委员会
homebrew
私有 1Password,并将他们添加到“plc”组中。当他们不再是 PLC 成员时,撤销或降级他们对上述所有内容的访问权限。
如果维护者当选为 Homebrew 的 技术指导委员会
当他们不再是 TSC 成员时,撤销或降级他们对上述所有内容的访问权限。
项目负责人、另一名 PLC 成员(最好是维护者)和另一名 TSC 成员应成为 GitHub 和 Slack 上的所有者
machomebrew
私有 Slack 中将他们设为所有者homebrew
私有 1Password 中将他们设为所有者当他们不再是所有者时,撤销或降级他们对上述所有内容的访问权限。
不符合资格或不愿意成为 Homebrew 维护者但已持续参与 Homebrew 社区的人员,经 项目领导委员会 多数票同意,可加入 Homebrew GitHub 组织成为 成员。
当被接纳为成员时
machomebrew
私有 Slack 上的 #members 频道(并确保他们已阅读 通信准则),并要求他们在那里使用他们的真实姓名(而不是他们在 GitHub 等网站上可能使用的化名)。如果他们有兴趣从事运维/基础设施/系统管理工作
homebrew
私有 1Password 并将他们添加到“ops”组。如果他们对从事安全工作感兴趣
homebrew
私有 1Password 并将他们添加到“security”组。请参阅 Homebrew 治理 了解个人会员资格何时到期。