GOVERNANCE / LIGHTWEIGHT MAINTAINER MODEL

One set of principles, applied consistently.

The project is run by a lightweight maintainer model: few formal roles, but the same decision principles applied every time.

Decision principles

  • Keep the core lean and broadly reusable
  • Prefer plugins for ecosystem-specific integrations
  • Require reproducible fixtures for behavior changes where practical
  • Document compatibility and migration impact
  • Record the rationale for large or breaking decisions publicly

Roles

The project is currently run by a single maintainer. A canonical maintainer list, review rights and release ownership will be published here as the contributor base grows.

Proposals

A large proposal should start as a public problem statement with a fixture or example, before any implementation. It should say explicitly whether the work belongs in core, a plugin, documentation or tooling.