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, @toxakara, a member of the packvium GitHub organisation, where the public package repositories live. A fuller 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.

Correcting a published error

This site has no registry to yank and no version to patch - a correction ships the next time it deploys. The claim is checked against its real source before anything changes, the fix lands in every locale together, and if the same mistake could recur in a different sentence, it is added to the site's own automated checks so CI catches it next time instead of waiting for another review.