Skip to content

docs: CODEOWNERS-POLICY.adoc + bring CODEOWNERS into Rule 1 compliance - #213

Merged
hyperpolymath merged 1 commit into
mainfrom
docs/codeowners-policy
Jul 29, 2026
Merged

docs: CODEOWNERS-POLICY.adoc + bring CODEOWNERS into Rule 1 compliance#213
hyperpolymath merged 1 commit into
mainfrom
docs/codeowners-policy

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Two of the eight files #204 tracks, landed together because writing the policy document while violating the policy would have been self-contradictory.

.github/CODEOWNERS carried six lines, every one naming the sole maintainer:

* @hyperpolymath /rust-core/ @hyperpolymath /elixir-orchestration/ @hyperpolymath /src/vcl/ @hyperpolymath /container/ @hyperpolymath /.github/ @hyperpolymath

The catch-all * and the /.github/ line are precisely the two shapes hyperpolymath/standards CODEOWNERS-POLICY.adoc Rule 1 prohibits for solo-maintained repos, and the prohibition is not stylistic:

  • * requested a review from the sole maintainer on every PR, including every Dependabot bump — and this repo gets a lot of those.
  • /.github/ fired again on workflow changes, so CI-touching PRs generated two requests rather than one.
  • Neither gated anything. A sole maintainer cannot be blocked on their own review, and the Base ruleset requires 0 approving reviews, so no merge was ever actually held by these lines.
  • Attribution never depended on them: every file carries an SPDX header and reuse lint enforces that at 100%.

Replaced with the canonical comment-only header. Rule 3 (co-owner removal needs explicit confirmation) is not engaged — no line mapped to anyone other than the sole maintainer, so nobody's review gate was removed. Worth stating explicitly, since "deleting CODEOWNERS lines" is otherwise exactly the shape of change Rule 3 exists to prevent.

CODEOWNERS-POLICY.adoc deliberately references the estate policy rather than forking it — a second copy would drift, and then the repo would have two policies disagreeing. What it adds is the conformance record: what this repo does, which rules are engaged, and why the removed lines were noise rather than control. That is the part that cannot live upstream.

The doc names GOVERNANCE.adoc as not-yet-written and blocked on the TPCF perimeter ruling, rather than linking to it as though it exists. The gap is visible instead of implied.

Verified: tests/doc-consonance-gate.sh passes (no "VeriSim Query Language" misnomer); reuse lint compliant — REUSE.toml already globs **/*.adoc to CC-BY-SA-4.0, so the new file needed no annotation change.

Summary

Closes #

Type of change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (would change existing behaviour)
  • 🕳️ Soundness fix (fixes a checker/proof false-negative)
  • 📖 Documentation
  • 🧹 Refactor / tech debt (behaviour-preserving)
  • ⚡ Performance
  • 🔧 Build / CI / tooling

How has this been verified?

Checklist

  • My commits are signed (git commit -S).
  • I ran the project's own checks/tests locally and they pass.
  • New files carry the correct SPDX-License-Identifier (code/config MPL-2.0,
    prose CC-BY-SA-4.0); I did not relicense existing files.
  • Docs are updated, and no public claim now overstates what the code does.
  • I have not introduced a soundness hole (or I have flagged where I might have).

Notes for reviewers

Two of the eight files #204 tracks, landed together because writing the policy
document while violating the policy would have been self-contradictory.

`.github/CODEOWNERS` carried six lines, every one naming the sole maintainer:

    * @hyperpolymath
    /rust-core/ @hyperpolymath
    /elixir-orchestration/ @hyperpolymath
    /src/vcl/ @hyperpolymath
    /container/ @hyperpolymath
    /.github/ @hyperpolymath

The catch-all `*` and the `/.github/` line are precisely the two shapes
`hyperpolymath/standards` CODEOWNERS-POLICY.adoc Rule 1 prohibits for
solo-maintained repos, and the prohibition is not stylistic:

* `*` requested a review from the sole maintainer on **every** PR, including
  every Dependabot bump — and this repo gets a lot of those.
* `/.github/` fired again on workflow changes, so CI-touching PRs generated two
  requests rather than one.
* Neither gated anything. A sole maintainer cannot be blocked on their own
  review, and the Base ruleset requires 0 approving reviews, so no merge was
  ever actually held by these lines.
* Attribution never depended on them: every file carries an SPDX header and
  `reuse lint` enforces that at 100%.

Replaced with the canonical comment-only header. Rule 3 (co-owner removal needs
explicit confirmation) is **not** engaged — no line mapped to anyone other than
the sole maintainer, so nobody's review gate was removed. Worth stating
explicitly, since "deleting CODEOWNERS lines" is otherwise exactly the shape of
change Rule 3 exists to prevent.

`CODEOWNERS-POLICY.adoc` deliberately **references** the estate policy rather
than forking it — a second copy would drift, and then the repo would have two
policies disagreeing. What it adds is the conformance record: what this repo
does, which rules are engaged, and why the removed lines were noise rather than
control. That is the part that cannot live upstream.

The doc names `GOVERNANCE.adoc` as not-yet-written and blocked on the TPCF
perimeter ruling, rather than linking to it as though it exists. The gap is
visible instead of implied.

Verified: `tests/doc-consonance-gate.sh` passes (no "VeriSim Query Language"
misnomer); `reuse lint` compliant — `REUSE.toml` already globs `**/*.adoc` to
CC-BY-SA-4.0, so the new file needed no annotation change.
@gitar-bot

gitar-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown

Note

Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime.
Learn more

Code Review ✅ Approved

Adds CODEOWNERS-POLICY.adoc and updates CODEOWNERS to remove redundant catch-all rules, bringing the configuration into Rule 1 compliance. No issues found.

Auto-approved and auto-merge armed: No blocking issues found.
Please see Auto-approve Docs for details on setting custom approval criteria. — merges when pipeline and required approvals pass.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

@gitar-bot

gitar-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown

⚠️ Gitar auto-approved this PR but could not enable auto-merge: auto-merge is disabled for this repository — enable "Allow auto-merge" in the repository settings.

@gitar-bot gitar-bot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Gitar has auto-approved this PR and enabled auto-merge (configure)

@gitar-bot gitar-bot Bot added the gitar-approved Added by Gitar label Jul 29, 2026
@hyperpolymath
hyperpolymath merged commit 913a773 into main Jul 29, 2026
42 checks passed
@hyperpolymath
hyperpolymath deleted the docs/codeowners-policy branch July 29, 2026 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gitar-approved Added by Gitar

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant