Merge pull request #655 from swinslow/add-guidance-links

Add links to attribution recommendations
cncf · Oct 18, 2023 · fb57be1 · fb57be1
2 parents 9eff84d + 0c69dcc
commit fb57be1
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 0 deletions.
diff --git a/copyright-notices.md b/copyright-notices.md
@@ -61,6 +61,9 @@ You _should not_ change or remove someone else's copyright notice unless they
 have expressly permitted you to do so. This includes third parties' notices in
 pre-existing code.
 
+For additional details regarding attribution notices for third party code used
+in CNCF projects, see the [CNCF attribution recommendations] document.
+
 ## Why not list every copyright holder?
 
 There are several reasons why CNCF doesn't require or recommend trying to list
@@ -80,3 +83,5 @@ every copyright holder for contributions to every file:
   notices.
 - The specific individual or legal entity that owns the copyright might not be
   known to the contributor; it could be you, your employer, or some other entity.
+
+[CNCF attribution recommendations]: https://github.com/cncf/foundation/blob/main/recommendations-for-attribution.md
diff --git a/license-notices.md b/license-notices.md
@@ -8,6 +8,9 @@ There are several reasons to include notices on a file-by-file basis, rather tha
 
 There is no one mandatory way in which license notices need to be provided. Following are some options for ways to provide notices in various use cases.
 
+For additional details regarding attribution notices for third party code used
+in CNCF projects, see the [CNCF attribution recommendations] document.
+
 ### Original content for CNCF projects
 
 Under the [CNCF charter], section 11, source code is to be made available under the Apache License, version 2.0 (Apache-2.0) and documentation is to be made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0).
@@ -101,3 +104,4 @@ This could be done in the file itself, or in a root-level file such as THIRD-PAR
 The [REUSE Software Initiative](https://reuse.software/spec/) also contains recommendations for placing license texts within a `/LICENSES/` directory.
 
 [CNCF Charter]: https://github.com/cncf/foundation/blob/master/charter.md
+[CNCF attribution recommendations]: https://github.com/cncf/foundation/blob/main/recommendations-for-attribution.md