Small enough that one pull request changes it

Where to talk

Contributing

Start with a good first issue. Each one says which files to change, how to test it, and when it's done. Say you're taking it on the issue, and it's yours. Small fixes (a typo, a doc, an obvious bug) can go straight to a pull request. For anything bigger, open an issue or a discussion first, so nobody spends a weekend on something that clashes with the roadmap.

Rust helps for most of the code. It isn't needed for docs and copy, and those fixes count just as much. CONTRIBUTING.md takes you from clone to merged pull request.

What won't change

• It stays open source, under the MIT License.
• No CLA, ever, and no copyright assignment. You keep the copyright to your work and sign off each commit under the Developer Certificate of Origin with git commit -s. Because copyright stays with everyone who contributed, no single person or company can take the project closed.
• Sponsors get visibility, not control. Every feature lives in the open source project, and nobody can pay to have one held back from everyone else.

While the project is small, I make the final call, in public. Anyone who contributes steadily and reviews other people's work can be invited to become a maintainer, and once maintainers come from more than one organization, the plan is to move the project, its trademark and its domains to a neutral foundation. It's all in GOVERNANCE.md.

The Code of Conduct applies everywhere in the project. Report a problem to [email protected]. Thinking of sponsoring? Write to [email protected].

Contributors

Everyone with a commit on main, most commits first. The next name could be yours.