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

Align licensing policy and attribution with the house standard

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-26 21:15:13 +00:00
parent c034b7e709
commit 3883a5042d
12 changed files with 1350 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/release.md
View File

@@ -95,6 +95,21 @@ begin with `# ConfigKit $release_version` and contain `Summary`, `Compatibility`
to current canonical contracts instead of copying their definitions. Do not create a
release note until there is a real candidate and reviewed content.
End each new release note with the footer required by the
[OSS policy](policy/oss.md#discoverability). For the selected version, use these
absolute Gitea URLs (replace every `VERSION` with the complete intended tag):
```markdown
[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/VERSION/docs/oss/attribution.md)
```
Confirm the three target files exist in the candidate and the version is correct
during ordinary note review. The future tag need not resolve remotely yet; do
not add publication-time network checks. ConfigKit publishes source tags with
checked-in notes, not separate hosted download pages. If a hosted release page
is used later, reuse the checked-in note as its body and retain this footer.
Do not retrofit published notes or add separate downloadable license assets.
## 4. Validate the source candidate
Before release validation, finish compatibility review, inspect the diff and file