Docs
Two kinds of writing live here: how to take part in the work, and how the work gets written down.
Taking part
VisionHow issues get claimed, what makes a pull request easy to merge, and the sign-off every contribution carries.
Respect people, their identities, their culture, and their work. Listen before responding.
Support • Frequently Asked Questions
Where to ask, in the order worth trying.
How to report a vulnerability privately.
The style handbook
9 of 9 written
The house style our documentation and commit messages follow, one rule to a page. Each rule is stated below, so you can find the one you need.
- Capitalization
- When to capitalize, and when to leave a word lowercase.
- Code in Text
- What to set in code font, and how to explain placeholders.
- Code Samples
- How to introduce and present a code sample.
- Colons
- A colon indicates that closely-related information follows.
- Commit Messages
- How to describe a change in the message that accompanies it.
- Dashes
- Which dash to use, and how it differs from a colon.
- Documenting Command-Line Syntax
- Recommendations for documenting command-line tools.
- Lists
- How to introduce and punctuate lists.
- Prefer People/Person-First Language When Appropriate
- Follow the community's own preference between person-first and identity-first language.
Not here yet
The OpenINF SDK arrives in Q4 2026, and its reference documentation arrives with it. Progress shows up in the news.