Community#
| Page | Covers |
|---|---|
| Governance | Valence favors no firmware, no vendor and no product |
| Contributing | Building the site, the two writing registers, and why no wire number is typed by hand |
| RFC process | How a protocol change is proposed, argued and decided |
The short version#
Valence is provided to the community as a tool. The specification is the product; the library is its reference implementation. The registry is the single source of truth for every number, and it is enforced by generation rather than by discipline.
Numbers released in a tagged version are permanent. They are never reused and never renumbered.
Where discussion happens#
Protocol change happens in pull requests against the registry and the specification, in the open. If a proposal is refused, the refusal is recorded with its reasoning, so the next person to have the same idea can read why.