Skip to content

Continuity: znmead holds Maintain again #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HackTuah merged 1 commit into from
Sep 23, 2026
Merged

Continuity: znmead holds Maintain again #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ apply here, and this page says what is particular to this repository.
| role | who | responsibilities |
|---|---|---|
| **Maintainer** | one person: the ScriptKittyOS organization's administrator, the `full` hex.pm owner of `beam_mcp_signer` (account `aylacroft`), and the address in `SECURITY.md` | decides what lands and when; reviews every pull request; keeps CI green; answers security reports on `SECURITY.md`'s commitments; tags (signed) and publishes releases; keeps this page, the roadmap and the CHANGELOG true |
| **Continuity holders** | two people, from 2026-09-23, the same as on `beam_mcp`: `znmead`, the Maintain role on this repository (re-invited on 2026-09-23 when the organization began requiring secure two-factor methods; pending his acceptance); Mike Hostetler (`mikehostetler`), the Maintain role here and `maintainer` ownership of `beam_mcp_signer` on hex.pm, so he alone covers every step from issue to published release; the organization requires secure two-factor authentication | if the maintainer cannot act, keep the project going within a week between them: triage and close issues, merge pull requests once CI is green, tag (signed with their own key, announced in the CHANGELOG with its fingerprint) and publish releases; decide nothing while the maintainer can |
| **Continuity holders** | two people, from 2026-09-23, the same as on `beam_mcp`: `znmead`, the Maintain role on this repository; Mike Hostetler (`mikehostetler`), the Maintain role here and `maintainer` ownership of `beam_mcp_signer` on hex.pm, so he alone covers every step from issue to published release; the organization requires secure two-factor authentication | if the maintainer cannot act, keep the project going within a week between them: triage and close issues, merge pull requests once CI is green, tag (signed with their own key, announced in the CHANGELOG with its fingerprint) and publish releases; decide nothing while the maintainer can |
| **Contributor** | anyone | proposes changes by pull request under `CONTRIBUTING.md`: signed off, tested, green; reports bugs and enhancements as issues; reports vulnerabilities privately |

There is no steering group and no vote. A decision is the maintainer's and is recorded in the
Expand Down