Participate
Ask a question about the draft, or propose a change to the protocol.
Get involved
In an issue, name the part of the specification your question applies to and what the text does not let you decide. A maintainer answers there.
How the specification changes
Normative text lives in the root spec-*.md files. Everything else, including the specification pages on this site, is a downstream copy.
Every change is a public pull request
Against the specification files, reviewed in the open. Editorial and non-normative fixes need nothing more than this.
A normative change states its rationale first
What breaks and what the change impacts, written before the code.
New behavior ships with tests
The reference implementation moves in the same release.
Two maintainers approve before merge
Maintainers are the editors of the current draft, listed in MAINTAINERS.md.
Interfaces may still change: v0.1.0 has not been through public consultation, which opens before v1.0 is pinned. Governance and the license split are recorded in specification governance.
Where PDPP is today
v0.1.0 is a normative draft.
LFDT Labs proposal accepted; repositories public under the PDP-Connect organization.
Core protocol v0.1.0 published as a normative draft alongside the forkable reference implementation.