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

Link licensing examples from the upstream policy repository

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-27 13:55:53 +00:00
parent a469273add
commit f7d054b551
1 changed files with 16 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/policy/oss.md
View File

@@ -1,6 +1,6 @@
# Open Source Licensing And Attribution Policy
**Base Policy Version:** 1.4
**Base Policy Version:** 1.5
**Last Updated**: 2026-09-27
@@ -20,7 +20,7 @@ Repositories adopting this policy should:
5. Remove this heading and its associated text.
Selected standard license texts are available in this template repository's
[reference collection](../oss/licenses/README.md). Copy the applicable texts,
[reference collection](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/docs/oss/licenses/README.md). Copy the applicable texts,
including companion licenses, into the adopting repository. The collection is a
convenience, not an exhaustive catalog or a required bundle; maintain the project's
own attribution entries and upstream notice links under this policy.
@@ -58,6 +58,15 @@ Use recognizable license filenames, such as `Apache-2.0.txt` or `LGPL-3.0.txt`.
A shared standard text may serve multiple entries. Keep explanations outside
license texts and preserve distinct versions and exceptions.
## Upstream Reference Examples
The linked examples are reference material hosted in the public policy
repository at a fixed commit. Retain these upstream links when adopting this
policy; do not copy the example collection into the application's or library's
`examples/` directory. Create the project's actual `COPYRIGHT` and attribution
files using the examples. Applicable license texts still belong locally in
`LICENSE` and `docs/oss/licenses/` as specified here.
## Project Licensing
Unless the author specifies otherwise, use **GPL version 3 or later**
@@ -72,8 +81,9 @@ license unless the author deliberately changes it. For mixed-purpose projects,
follow the author's selected scope rather than inferring different licenses for
individual packages.
Use the copyable [application COPYRIGHT](../../examples/licensing/application/COPYRIGHT)
or [library COPYRIGHT](../../examples/licensing/library/COPYRIGHT) as appropriate.
Use the upstream [application COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/application/COPYRIGHT)
or [library COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/library/COPYRIGHT)
to create the project’s root `COPYRIGHT` file.
Replace the project name, years, and holders with accurate information; do not
assume the maintainer owns every contribution or advance years automatically.
For another selected license, adapt the grant, SPDX expression, disclaimer, and
@@ -117,7 +127,8 @@ Each entry presents these five fields in order, with blank lines between them:
5. **Source repository link**, using `[Source](COMMIT_URL).` with no `Source:`
prefix or additional description.
Use the copyable [attribution example](../../examples/licensing/attribution.md).
Use the upstream [attribution example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/attribution.md)
to create the project’s `docs/oss/attribution.md`.
Its three illustrative entries demonstrate a normal entry, omission of an
unavailable copyright statement, and multiple copyrights and license texts.
Replace the uppercase placeholders and illustrative URLs with actual component