How to be a maintainer

Theory of maintainership:

Someone always has the keys to the kingdom. Sometimes it is us. Being a maintainer is a position of trust and requires good judgement moreso even than skill

Steps:

1. Contribute to CASA via making PRs and/or opening issues and/or helping in slack
2. Post somewhere (usually in slack, but possibly also in a PR or github issue comment) "Hey, I might be interested in being a maintainer"
3. A conversation ensues. Ask questions!
4. current maintainer pings Sean & team to say what's up
5. set you up with permissions:
6. • heroku deploy permissions
7. • github maintainer permissions
8. • slack maintainer channel invite

Tasks that maintainers split up among themselves:

1. deploy weekly (we take turns, currently friday afternoons)
2. Review and merge PRs - friendly is good (someone needs to do it, but it doesn't have to be you)
3. Answer questions in slack
4. Help out with urgent code changes as needed (if available)
5. Talk to stakeholders. Make github issues of stakeholder asks.

Who are the current maintainers? https://github.com/rubyforgood/casa/wiki/Who's-who%3F

Right now, people who sign up to be "team leads" for Ruby for Good events are suddenly "maintainers"

Please ask questions! You can find us in #casa on rubyforgood slack