Small changes need one approval
A bug fix or a documentation change is merged when one maintainer who did not write it approves and the checks pass.
Maintainers
Nine volunteers who say no kindly.
Maintainers review pull requests, cut releases and answer security reports in their own time. They are chosen from regular contributors, serve for as long as they want to and can step back at any moment without explanation.
The maintainers
Reachable on the discussion board, and by email for anything private.
- Ayesha RahmanRelease manager and PDF renderer
- Jonas EriksenParser and core API
- Tiago BarrosTranslations and documentation site
- Chiamaka ObiPlugins and security
How decisions are made
Public changes need a proposal
Anything that changes the public API is written up, discussed for at least two weeks and accepted only when no maintainer objects.
Disagreement is settled by writing
If maintainers differ, they each state the trade-off in the proposal thread. When consensus is not reached, a majority vote of the active maintainers decides.
How someone becomes a maintainer
- Months 1–3
Contribute regularly · Contributor
Land at least ten merged pull requests across code, tests or documentation, and take part in review discussions.
- Months 3–6
Review other people's work · Reviewer
Join the reviewers group, with commenting rights on every pull request and a mentor from the maintainers.
- After 6 months
Nominated by a maintainer · Maintainer
Any maintainer can nominate a reviewer. The group votes in private and welcomes the new maintainer on the next call.