aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMike McQuaid2015-10-16 09:27:30 +0100
committerMike McQuaid2015-10-16 09:27:30 +0100
commita9b3c9200e3e43d024c067920688a0a429ca022a (patch)
tree0385ebd6197d6e128fece12bfea34413ac1bdb96
parente4de6907fd3c662c406fd903e2a6562da27d06cc (diff)
downloadbrew-a9b3c9200e3e43d024c067920688a0a429ca022a.tar.bz2
New-Maintainer-Checklist: general updates.
-rw-r--r--share/doc/homebrew/New-Maintainer-Checklist.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/share/doc/homebrew/New-Maintainer-Checklist.md b/share/doc/homebrew/New-Maintainer-Checklist.md
index 834360772..ba66b0eff 100644
--- a/share/doc/homebrew/New-Maintainer-Checklist.md
+++ b/share/doc/homebrew/New-Maintainer-Checklist.md
@@ -7,7 +7,7 @@ First, send them the invitation email:
```
The Homebrew team and I really appreciate your help on issues, pull requests and
-your contributions around making our testing better.
+your contributions around $THEIR_CONTRIBUTIONS.
We would like to invite you to have commit access. There are no obligations,
but we'd appreciate your continuing help in keeping on top of contributions.
@@ -36,14 +36,15 @@ Thanks for all your work so far!
If they accept, follow a few steps to get them set up:
-- [x] Invite them to the [**@Homebrew/core** team](https://github.com/orgs/Homebrew/teams/core) to give them write access to all repositories (but not administrator access yet)
+- [x] Invite them to the [**@Homebrew/maintainers** team](https://github.com/orgs/Homebrew/teams/maintainers) to give them write access to all repositories (but don't make them owners yet)
- [x] Ask them to sign up for a [Bintray](https://bintray.com) account and invite them to [Bintray's Homebrew organisation](https://bintray.com/homebrew/organization/edit/members) as a member (but not administrator access yet) so they can publish new bottles
- [x] Add them to the [Jenkins' GitHub Authorization Settings admin user names](http://bot.brew.sh/configureSecurity/) so they can adjust settings and restart jobs
- [x] Add them to the [Jenkins' GitHub Pull Request Builder admin list](http://bot.brew.sh/configure) to enable `@BrewTestBot test this please` for them
- [x] Invite them to the [`homebrew-dev` private maintainers mailing list](https://groups.google.com/forum/#!managemembers/homebrew-dev/invite)
+- [x] Invite them to the [`machomebrew` private maintainers Slack](https://machomebrew.slack.com/admin/invites)
- [x] Add them to [Homebrew's README](https://github.com/Homebrew/homebrew/edit/master/README.md)
- [x] Encourage them to enable [GitHub's Two Factor Authentication](https://help.github.com/articles/about-two-factor-authentication/)
-After a few weeks/months with no problems consider making them administrators on the [**@Homebrew/owners**](https://github.com/orgs/Homebrew/teams/owners) and [Bintray](https://bintray.com/homebrew/organization/edit/members) teams.
+After a few weeks/months with no problems consider making them [owners on the Homebrew GitHub organisation](https://github.com/orgs/Homebrew/people) and [administrators on Bintray](https://bintray.com/homebrew/organization/edit/members).
Now sit back, relax and let the new maintainers handle more of our contributions.