Maintainers
A maintainer merges changes, cuts releases, and sets direction. This page lists the real people doing that work — it is not an about-the-company page.
Ashutosh Panigrahi
Founder & Lead MaintainerResponsibility: Overall direction, model releases, governance
Bus factor: 1
This project has a single maintainer. That is stated plainly here because it is a real risk you should weigh before depending on the software: if the maintainer is unavailable, releases slow down, reviews queue, and security fixes may be delayed. We do not hide this behind a team page.
Mitigations, such as they are: everything is released under a permissive licence with the full source and history public, so anyone can fork and carry the work forward; decisions are recorded in public issues rather than private channels, so context is not lost with one person; and the roadmap is public, so nothing is secretly in flight.
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 on an issue and the maintainer will help you find the right scope of responsibility.
How decisions are made
The full process — roles, consensus-seeking, and how to change governance itself — is documented on the governance page.
Recognition
Contributions are recorded in the public repository history and in each release's notes. We do not currently run a separate contributor-recognition programme; the commit log is the record.