Governance

@adidshaft is the initial maintainer. The maintainer reviews releases, compatibility pins, security reports and project direction.

Propose a change

Open an issue that states the problem, evidence and tradeoffs. Coordinate protocol changes with both SDKs. Small typo fixes can go directly to a pull request (PR).

Record decisions and reasons in the source or linked issue. Use repeatable evidence to resolve technical disagreements. The maintainer decides unresolved scope questions. Use the private appeal path for conduct concerns.

Become a maintainer

Additional maintainers can join after sustained, reviewed contributions. The invitation and acceptance must be public and must define responsibilities. Documentation, tests and software or hardware verification all count. Contributor status does not automatically grant maintainer access.

Contribution terms

Changes receive review and credit in Git history and release notes. Original contributions use Apache-2.0. No additional contributor license agreement (CLA) or sign-off is required. Contributors remain responsible for AI-assisted code and test claims.

The owner retained the current project and repository names for public source publication. Future branding changes require an explicit project decision. See the roadmap.