Repository navigation
Conversation
Adds the Policy on Policies, which defines what a policy is in this repository, what a policy document must contain, and how one is proposed, approved, amended, and retired. Supporting material and repository changes that go with it: - policies/2026-10-30-policy-on-policies/approvers/ records the designated approver and alternate for MOC, BU, and Red Hat, and the teams that may be named as a policy's responsible-team. It is supporting content, kept as <name>/README.md so the link resolves both on GitHub and on the published site, and excluded from the policies collection so it is not listed as a policy in its own right. The approver and contact entries are still TBD. - The repository README gains an "Approving a policy" section summarising the process, including the steps taken once the last institution approves. It states that the policy governs where the two differ. The heading is named rather than left as "Approval" so its anchor does not shift when sections are added above it. Also corrects the policy directory path in the "Creating a new policy" example. - templates/policy is rebuilt to produce a conforming policy: the eight required sections in order, the "None." convention, and a Version History table with a Type column. A policy carries no approval date in its frontmatter. The date it was last approved is the date of the most recent Normative row of its Version History, so there is a single place to update and no second copy that can drift. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
This looks good. My only question is actually not about the policy docs content, but about what a "Responsible team" is defined as. It seems that there are NIST examples of responsible teams given, but there is no analog to this example in the MOC or Red Hat goups. Do we just consider the Red Hat folks all together as a responsible team, and same for the current MOC folks?
Discussed the above questions and the intent is to define an appropriate responsible team as needed for each policy, not matter what org they are from. The org is not the the responsible team. Makes sense.
As an extra note, we should revise the existing already-approved policy as a low priority task when we have time. This is so that all the policies will be consistent eventually.
This all seems workable.
hpdempsey
left a comment
There was a problem hiding this comment.
Approved after some discussion. No changes needed.
|
|
||
| Each institution designates one approver for policy pull requests, and one | ||
| alternate who records that institution's approval when the designated approver | ||
| is the author of the pull request. These roles are per institution, not per |
There was a problem hiding this comment.
or the designated approver is not available.
Should we cover what to do if both are unavailable or is that over the top?
There was a problem hiding this comment.
As written the policy change will remain unapproved until one of them is available. That seems the right response beyond the ramp up period.
The official list of approvers is supplemental content so the approvers can update the list if someone will be unavailable for a while. However, the fact that it is one per partner is normative content so a partner can't be completely excluded.
| > The `main` ruleset does not dismiss approvals on push, so this final commit | ||
| > does not invalidate the approvals already recorded. The ruleset requires two | ||
| > approving reviews; the requirement that one come from each institution is | ||
| > enforced by the approvers, not by GitHub. |
There was a problem hiding this comment.
we could enforce via github - I agree we should not at this time.
There was a problem hiding this comment.
I agree with both statements - automatic enforcement is a nice to have for now. We can consider adding a covenant that approvers agree in the future for this and other aspects of governance. But we don't need this now and we'll have a better sense of what we need later.
|
@msdisme @hpdempsey I made two small changes to the text.
Let me know what you think. |
Adopts a Policy on Policies: what counts as a policy in this repository, what a
policy document must contain, and how one is proposed, approved, amended, and
retired.
This is the first pull request to follow the process it defines, so it is also
the bootstrap: please read it as the rule you will be held to, not just as a
document. It needs an approval from each of MOC, BU, and Red Hat, and stays
open at least ten business days from the announcement so that people who are
not approvers can comment.
What's here
policies/2026-10-30-policy-on-policies/README.md— the policy.policies/2026-10-30-policy-on-policies/approvers/— a supportingdocument listing the designated approver and alternate for each institution,
and the teams that may be named as a policy's
responsible-team. Entries areTBD; see "Before this can merge" below.README.md— a new "Approving a policy" section summarising the processfor people working through a PR. It states that the policy governs where the
two differ, so that editing the README cannot quietly change the approval
rules.
templates/policy/— rebuilt so that copying it produces a conformingpolicy. The previous template was a two-line stub.
The decisions worth your attention
These are the normative choices. Everything else follows from them.
substitution. Any one institution can block indefinitely.
restarts the clock; an editorial correction does not.
are normative and need the full process. Supporting Documents and Related
Policies are supporting content, which the responsible team can change with
the usual two reviews. The intent is that facts changing on someone else's
schedule — supported OS releases, who holds a role — live in supporting
documents so that routine reality does not require a policy amendment.
when the policy was first proposed and never change, so published URLs stay
valid across revisions. Retired policies stay in place rather than being
deleted.
date of the most recent
Normativerow of its Version History. One place toupdate, no second copy to drift.
approver. The approvers list is supporting content, so without this
carve-out one institution could change another's representative.
a single approval from any institution, with a PR labelled
editorial. Anyapprover can object that a change labelled editorial is substantive, which
returns it to the full process.
Before this can merge
approvers/table is filled in. Replying in this thread is enough.business days can be counted.