From b1a49da4a47629238ed42304899055bd4d9f4808 Mon Sep 17 00:00:00 2001 From: Ayla Croft Date: Wed, 23 Sep 2026 16:56:27 -0400 Subject: [PATCH] Continuity: znmead has accepted Maintain again; the pending wording goes Measured 2026-09-23: GitHub lists znmead as a collaborator with role maintain on beam_mcp and beam_mcp_signer, no invitation pending, after the re-invitation the organization's secure-2FA requirement made necessary. The pages said pending; they now say he holds it. Copy only. Signed-off-by: Ayla Croft --- GOVERNANCE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index a1d9e77..710616e 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -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