eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correct policy references and restore upstream wording

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-28 00:45:13 +00:00
parent 897203dd8f
commit faf5ff8fa1
2 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/policy/documentation.md
View File

@@ -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

9
docs/policy/oss.md
View File

@@ -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.