From faf5ff8fa1a69bc0ac82abc792357e25f6203f4e Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Mon, 28 Sep 2026 00:45:13 +0000 Subject: [PATCH] Correct policy references and restore upstream wording --- docs/policy/documentation.md | 3 +-- docs/policy/oss.md | 9 ++++----- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/policy/documentation.md b/docs/policy/documentation.md index dcfc8e1..1f6c817 100644 --- a/docs/policy/documentation.md +++ b/docs/policy/documentation.md @@ -99,8 +99,7 @@ secret values. Create supporting documents for existing interfaces and responsibilities when substantive content is available. -Do not create empty owners. Unvalidated candidate and publication work has -the temporary exception recorded in the release policy. +Do not create empty owners. ## Boundary Rules diff --git a/docs/policy/oss.md b/docs/policy/oss.md index 731473e..baf4d46 100644 --- a/docs/policy/oss.md +++ b/docs/policy/oss.md @@ -174,11 +174,10 @@ grant in `COPYRIGHT` and the attribution document. ConfigKit's [README](../../README.md) contains the two required statements: one linking to the project grant and one linking to attribution. -Each new checked-in release document must end with links whose visible text is -`COPYRIGHT | LICENSE | ATTRIBUTION`. Use absolute URLs to those files at the -release's immutable tag or corresponding immutable source revision so the links -work for source-only Gitea publication. Where a hosted download page is used, -it carries the same links. This release navigation is distinct +Each new checked-in release document and its hosted download page must end +with links whose visible text is `COPYRIGHT | LICENSE | ATTRIBUTION`. Use absolute +URLs to those files at the release's immutable tag or corresponding immutable source +revision so the links work in both locations. This release navigation is distinct from upstream component links, which must use the imported commit. Reuse the checked-in release document as the hosted release body where supported.