This document describes how the @perishdev organization is governed. It applies org-wide to any repository that does not provide its own GOVERNANCE.md.
It is intentionally lightweight: perishdev is a small organization, and this document reflects that reality rather than aspiring to a large-project structure it does not need.
Maintainers are responsible for the direction, review, and upkeep of the org's repositories. They:
- Triage and respond to issues, discussions, and pull requests.
- Review and merge changes.
- Cut releases and keep the community health files (this repo) current.
- Uphold the Code of Conduct.
The maintainers team is @perishdev/maintainers, which is the global code owner across the org (see CODEOWNERS).
Anyone who opens an issue, starts a discussion, or submits a pull request is a contributor. Contributing does not require any formal status — see the Contributing Guide.
Decisions are made by the maintainers, favoring lazy consensus: a proposal (an issue, discussion, or pull request) is considered accepted if no maintainer raises a blocking objection within a reasonable time. Where consensus cannot be reached, the maintainers decide together; disagreements are resolved through discussion, not process.
Everyday changes (bug fixes, docs, small improvements) need only the normal pull-request review. Larger or hard-to-reverse changes — new policies, breaking changes, changes to these community health files — should be raised as an issue or discussion first so the approach can be agreed before work begins.
Maintainership is offered to contributors who have shown sustained, high-quality involvement and good judgment. There is no application process; existing maintainers extend an invitation. New maintainers are added to the @perishdev/maintainers team.
Changes to governance follow the same process as any other change: open a pull request against perishdev/.github and reach maintainer consensus. Because this file is inherited org-wide, consider the blast radius before editing.
- Conduct concerns: follow the Code of Conduct.
- Security vulnerabilities: follow the Security Policy — do not open a public issue.
- Anything else: see SUPPORT.md.