Skip to content

Commit

Permalink
New-Maintainer-Checklist: there are multiple places we list maintainers
Browse files Browse the repository at this point in the history
- I raised a PR for adding myself to the README. CI failed because the
  README had changed without the man pages changing too. Then I had to
  amend my "hello!" commit which was slightly embarrassing.
- Document that there are multiple places, and suggest `brew man` to
  generate man pages, so that the next people have it easier.
  • Loading branch information
issyl0 committed May 27, 2019
1 parent 515aef9 commit dd92fdf
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/New-Maintainer-Checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ If they accept, follow a few steps to get them set up:
- Invite them to the [`machomebrew` private maintainers Slack](https://machomebrew.slack.com/admin/invites) (and ensure they've read the [communication guidelines](Maintainer-Guidelines.md#communication)).
- Ask them to disable SMS as a 2FA device or fallback on their GitHub account in favour of using one of the other authentication methods.
- Ask them to (regularly) review remove any unneeded [GitHub personal access tokens](https://github.com/settings/tokens).
- Add them to [Homebrew/brew's README](https://github.com/Homebrew/brew/edit/master/README.md).
- Add them to Homebrew/brew's README, run `brew man` and commit the changes.

If they are interested in doing system administration work or Homebrew/brew releases:

Expand Down

0 comments on commit dd92fdf

Please sign in to comment.