Skip to content

Maintainers

This file lists the GenoLeWM project maintainers. Maintainers are the points of contact for code review, security reporting, and conduct issues.

Current maintainers

Additional maintainers will be added as the project grows; PRs adding a new maintainer require sign-off from at least one existing maintainer.

Roles

  • Project lead. Final say on RFC acceptance, release approval, and scope disputes. Stewards the overall direction.
  • Subsystem maintainer. Owns one of the subsystems listed in rfcs/README.md; reviews PRs in that area.
  • Security contact. Receives reports via GitHub Security Advisories or the address in SECURITY.md.

How to become a maintainer

  • Sustained, high-quality contributions (RFC reviews, implementation PRs, eval reports).
  • Demonstrated alignment with the project's privacy / safety frame.
  • Sponsorship by an existing maintainer.

No formal time-on-project requirement, but in practice expect several months of substantial contribution before sponsorship.

Off-boarding

A maintainer may step down at any time. The maintainer list is updated in the same PR. There is no "emeritus" tier; the public Git history is the record.