Skip to content

refactor(config): rename role_flags.pmc_member → governance_member#636

Merged
potiuk merged 2 commits into
mainfrom
refactor/governance-member-flag
Jun 29, 2026
Merged

refactor(config): rename role_flags.pmc_member → governance_member#636
potiuk merged 2 commits into
mainfrom
refactor/governance-member-flag

Conversation

@potiuk

@potiuk potiuk commented Jun 29, 2026

Copy link
Copy Markdown
Member

What

Makes the user-config governance-authorisation flag organization-agnostic
(the deliberate keep noted in #633). The flag answers "is this user
authorised under the project's governance.cve_allocation_gate?" — for
the ASF organization that gate is pmc-member, but the flag itself
shouldn't be ASF-named.

  • role_flags.pmc_memberrole_flags.governance_member in the user.md
    template + the structured-question batch (skills/setup/adopt.md).
  • security-cve-allocate reads role_flags.governance_member; the
    explanation now frames it as a generic boolean resolved against the
    gate, with pmc-member as the ASF example rather than the hardcoded
    default name.
  • Eval fixtures (security-cve-allocate step-3) updated to provide
    governance_member.

Verification

No pmc_member remains anywhere; skill-and-tool-validate EXIT 0;
markdownlint, lychee, placeholder check green. Skill and both eval
fixtures consistently use governance_member.

🤖 Generated with Claude Code

Tester added 2 commits June 29, 2026 07:46
Make the user-config governance-authorisation flag organization-agnostic.
The flag answers "is this user authorised under the project's
`governance.cve_allocation_gate`?" — for the ASF organization that gate
is `pmc-member`, but the flag itself should not be ASF-named.

- `role_flags.pmc_member` → `role_flags.governance_member` in the user.md
  template + the structured-question batch (skills/setup/adopt.md).
- security-cve-allocate reads `role_flags.governance_member`; the
  parenthetical now explains it as a generic boolean resolved against
  the gate, with `pmc-member` as the ASF example rather than the
  hardcoded default.
- Eval fixtures (security-cve-allocate step-3) updated to provide
  `governance_member`.

Completes the deliberate keep noted in the governance-vocabulary sweep.

Generated-by: Claude Code (Opus 4.8)
…e eval

Extends the governance_member rename to the spots that still named PMC:

- AGENTS.md + docs/setup/unadopt.md: "PMC status" → "governance
  membership" (and "PMC status, ASF committer role" → "Governing-body
  membership, committer role" in the external-content authority test).
- security-cve-allocate step-3 eval: rename the fixtures
  case-1-pmc-member → case-1-governance-member and
  case-2-non-pmc → case-2-non-member (cases are auto-discovered by
  iterdir, no references to update); "## User PMC status" → "## User
  governance membership"; output-spec + expected.json key
  `pmc_path` → `governance_member_path`; README "PMC vs non-PMC" →
  "member vs non-member". Vulnogram URL assertion left as-is — that
  tests the ASF CVE-tool backend, a separate axis.

Left: committer-onboarding's `committer_governance.model: asf-pmc` row,
which already enumerates non-ASF alternatives (github-codeowners,
maintainer-roster) and belongs to the ASF-scoped contributor-growth
family.

Validator EXIT 0; output-spec ↔ expected.json keys consistent.

Generated-by: Claude Code (Opus 4.8)
@potiuk potiuk merged commit 32e53a7 into main Jun 29, 2026
29 checks passed
@potiuk potiuk deleted the refactor/governance-member-flag branch June 29, 2026 06:09
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.

1 participant