How to be a maintainer

We have no idea yet! TBD

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"

What do we expect maintainers to do?

1. Currently, only maintainers merge PRs
2. Currently, only maintainers approve or request changes on PRs
3. Go thru in-progress issues and touch base with assignees. Unassign after (some amount of) non-responsiveness. TODO- make a guideline just for this...
4. [backlog grooming] Read thru all the Todo issues and add more details, check it still needs doing, add screenshots
5. Host weekly “office hours” where contributors can drop in to ask questions, pair program, or just say hi (optional- we don't always have to have office hours, but we like having them)
6. Attend stakeholder meetings (required for PM maintainers) - not required but... really hard to do without (we don't want to exclude potential PMs! We can work something out...) It is possible to be a non-maintainer PM!
7. [PM] move cards to columns
8. [PM] after prod deploy, move all QA tickets to Done column - can we automate that? With github actions
9. Deploy to prod (currently every friday) - including sending release announcement email to stakeholders
10. Someday there will be SLA/SRE/oncall responsibilities...
11. Answer questions on slack
12. Answer questions on github
13. Make sure that CI exists
14. Make sure that contributor onboarding and setup runs smoothly, somehow
15. Make sure that issues in TODO column have correct labels (Help Wanted, other tags as appropriate)

What can non-maintainers do?

1. File a github chore, feature, bug, or other issue
2. Pick up issues
3. Open PRs
4. Comment on a PR

Things that need to get done, but you don't have to be a maintainer to do it:

1. QA & bug hunting
2. Remove "help wanted" tag from issues in QA and beyond project columns https://github.com/rubyforgood/casa/issues/1362