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

Clarify attribution scope for development guidance and tooling

Browse Source
This commit is contained in:
Eric Rakestraw
2026-09-26 22:17:40 +00:00
parent dafa823981
commit 0243378009
1 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/policy/oss.md
View File

@@ -1,6 +1,6 @@
# Open Source Licensing And Attribution Policy # Open Source Licensing And Attribution Policy
**Base Policy Version:** 1.2 **Base Policy Version:** 1.3
**Last Updated**: 2026-09-26 **Last Updated**: 2026-09-26
@@ -29,10 +29,13 @@ own attribution entries and upstream notice links under this policy.
This policy defines project licensing conventions and a repeatable House Format This policy defines project licensing conventions and a repeatable House Format
for upstream attribution and license notices. It covers the project's own code for upstream attribution and license notices. It covers the project's own code
and upstream components incorporated into or distributed with the project, and upstream components incorporated into or distributed with the application
including relevant transitive dependencies and or library, including relevant transitive dependencies and copied code or assets.
copied code or assets. Treatment follows the component's terms and actual use, Treatment follows the component's terms and actual use, rather than its
rather than its classification as a direct dependency. classification as a direct dependency.
Do not add attribution entries merely because a repository supplied development
guidance or tooling.
The baseline is a publicly available source repository with releases published The baseline is a publicly available source repository with releases published
alongside it. The format is independent of language, forge, and build system. alongside it. The format is independent of language, forge, and build system.