-
Notifications
You must be signed in to change notification settings - Fork 333
Bus factor
AJ Jordan edited this page Jun 1, 2021
·
9 revisions
This page exists to document who is responsible for different parts of the pump.io project, and who has backup access in case something happens to the primary contact.
| Component | Primary contact | Backup contact(s) |
|---|---|---|
| pump-io GitHub org | @strugee | @distopico, @cwebber or @evanp |
| e14n GitHub org | @evanp | @cwebber |
| pump.io GitLab org | @jankusanagi | @strugee, @sazius, or @larjona |
| Production pumabot deployment | @strugee | @jpwall |
| pump.io domain ownership | @evanp | None |
| pump.io domain DNS | @evanp | None |
| pump.io domain email | @evanp | None |
| npm package | @strugee | @evanp |
| http://pump.io webserver | GitHub | None |
#pump.io on Freenode op |
@larjona | @cwebber or @evanp |
#pump.io on Libera op |
@strugee | None |
#pump.io on Libera group contact |
@strugee | None |
| XMPP bridge | @strugee | None |
| XMPP room | @jankusanagi | @strugee |
| Snyk account | @strugee | None |
| ReadTheDocs account | @jankusanagi | @strugee |
Note that the pump-io GitHub org also includes access to the website contents and pumabot's code - "production pumabot deployment" refers to the actual live Node process that runs the bot that sits in #pump.io. The pump-io org also grants access to Travis CI and Coveralls.