|
| 1 | +# Governance |
| 2 | + |
| 3 | +## The Short Version |
| 4 | + |
| 5 | +Evan Phoenix ([@evanphx](https://github.com/evanphx)) created Puma and has final say on everything. [Maintainers](./MAINTAINERS) serve at his pleasure. |
| 6 | + |
| 7 | +## Access Levels |
| 8 | + |
| 9 | +We have two levels of access and privileges: |
| 10 | + |
| 11 | +### Gem Release Access |
| 12 | + |
| 13 | +This is kept intentionally small for security reasons. If you can cut a gem release, you can push code to a lot of production systems, so we're intentionally quite narrow here. |
| 14 | + |
| 15 | +**Current members:** Evan Phoenix ([@evanphx](https://github.com/evanphx)), Nate Berkopec ([@nateberkopec](https://github.com/nateberkopec)), and Richard Schneeman ([@schneems](https://github.com/schneems)). |
| 16 | + |
| 17 | +We cut releases ~whenever we feel like it. |
| 18 | + |
| 19 | +We may add or remove people from this group if releases start getting bottlenecked, but security is the priority. |
| 20 | + |
| 21 | +### Commit Bit ("Maintainers" or "Core Team") |
| 22 | + |
| 23 | +We give commit bit if you make significant contributions to minor (or major) releases, consistently over time. Show up, do good work, stick around. |
| 24 | + |
| 25 | +We review this access periodically, but we're looser with it than gem release access. |
| 26 | + |
| 27 | +If you have commit bit, we trust you enough to merge to `main` without necessarily getting review first. |
| 28 | + |
| 29 | +While all [security reports go to Evan directly](./SECURITY.md), maintainers will collaborate together on the fix. |
| 30 | + |
| 31 | +**Current members:** Everyone on the [Maintainers](./MAINTAINERS) list. |
| 32 | + |
| 33 | +## How Decisions Get Made |
| 34 | + |
| 35 | +Evan has final say on who gets these rights. Maintainers make suggestions and talk things through, but ultimately it's his call. |
| 36 | + |
| 37 | +In general, Puma maintainership works on the principle of [lazy consensus](https://openoffice.apache.org/docs/governance/lazyConsensus.html). |
| 38 | + |
| 39 | +We try to mostly work in public, so that more people outside the maintainer team can contribute and help out. |
| 40 | + |
| 41 | +If you have questions or want to suggest changes to how we run things, open an issue. |
0 commit comments