Contributing

Contributing here runs on a single rule: every change cites something in the specification, and that something already exists. It is the one genuinely unusual thing about this project, and reading it first will save you a round-trip.

Everything else is ordinary. Sign your commits off, be decent to the people around you, and file your issue wherever you can find a box for it — routing is a maintainer’s job, not yours.

You do not have to write code

The most useful contributions often are not code. Trying it and reporting what broke, fixing a paragraph that misled you, saying that a screen is hard to read, answering someone else’s question: all of it counts, and all of it follows the same one rule.

Start here

Cite the specThe one rule, the three cases you are likely to be in, and what happens if you skip it.

How change gets inThe org's own contributor guide, mirrored from the repository that owns it.

Sign-off and licensingWhy every commit needs -s, and what licence your work ships under.

Where does my issue go?One question decides the repository. If it does not, file anywhere.

Proposing a changeThe RFC flow: an issue form, a maintainer decision, and no git required of you.

Working with AI agentsThe five rules an agent and the person directing it are both held to.

Where to askFour destinations for a question, a problem, or an idea.

Reporting a vulnerabilityThe private disclosure path, and what is in scope.

Code of conductWhat is expected of everyone taking part, and how to report a problem.

Where to go next

If you are about to open a pull request, read the gates — the checks it will meet — and the repository map to find which of the eleven repos your change belongs in. For what is built, what is next and what the project stands on, see the project section.