How this project is run

Roles

• Contributors open issues and pull requests under the Code of Conduct.
• Reviewers triage issues and review pull requests in their area.
• Maintainers merge changes, cut releases, and set direction.

How decisions are made

1. Proposals start as an issue or a Discussion — never in a private channel.
2. Maintainers seek rough consensus in public. Where consensus is not reached, the lead maintainer decides and records the rationale on the issue.
3. Anything that changes the licence, the governance itself, or the public roadmap requires an announced decision with a comment period before it takes effect.

Maintainers

• Ashutosh Panigrahi — Founder & Lead Maintainer
  @ashutoshpanigrahi · Overall direction, model releases, governance

The full list lives on the maintainers page.

Becoming a maintainer

There is no fixed quota. A contributor who consistently lands good changes, reviews others' work fairly, and is reliable over time may be invited to become a reviewer, then a maintainer. If you are interested, say so in an issue and a current maintainer will help you find the right scope of responsibility.

Changing this document

Governance changes are made by pull request against this page, with an announcement in GitHub Discussions.