Contributing

Thanks for your interest. These repositories are maintained by one person, so the process is small but fixed.

Before you write code

1. Open an issue first. For a change, use the Planned change template. Typo fixes and dependency bumps don't need an issue.
2. Open questions go under ## To decide, one checkbox each. I answer them under ## Decisions and check each question off; a pull request merges only once every question is checked. Work started before a question is answered may need to change.

The pull request

• Link the issue (Closes #N).
• Fill in the PR template: a prose summary (it becomes the squash commit body) and the final decisions. A test should be seen failing before the change makes it pass.
• Update the documentation in the same PR when behavior changes.
• A small fix without decisions: write decisions: none in the PR description.

Review and merge

I review every pull request and merge it myself. Some changes need a manual check on real hardware before they can be merged; I'll say so on the pull request.

Setup, tests, and local checks are described in each repository's README or docs/.