Skip to content

docs(governance): only one person could administer Parsec - #120

Merged
jamesconwaydev merged 1 commit into
mainfrom
governance-admins
Nov 20, 2026
Merged

jamesconwaydev merged 1 commit into
mainfrom
governance-admins

Conversation

@jamesconwaydev

Copy link
Copy Markdown
Collaborator

Problem

Only James had admin rights on the repository, so if he became unavailable, nobody could change its settings, rulesets or access. OpenSSF's access_continuity criterion, at silver and gold, asks for exactly that continuity.

Change

@foothillsdigital is now an admin of parsec-html/parsec, and GOVERNANCE.md says so: either maintainer can change settings, rulesets and access, and keep Parsec going if the other can't. Release tags still need an admin and a key in .github/allowed_signers, which both maintainers have.

Tests

gh api repos/parsec-html/parsec/collaborators lists both maintainers with the admin role.

foothillsdigital is now an admin of the repository as well, so either
maintainer can change settings, rulesets and access, and keep Parsec
going if the other can't.

@foothillsdigital foothillsdigital left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked fa7e055. gh api repos/parsec-html/parsec/collaborators lists both of us as admin, so the sentence is true as it stands. It fits with the lines around it: release tags still need an admin and a key in allowed_signers, and both of us have both. Approving.

@jamesconwaydev
jamesconwaydev merged commit 2018e5b into main Nov 20, 2026
33 checks passed
@jamesconwaydev
jamesconwaydev deleted the governance-admins branch November 20, 2026 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants