cncf
/
foundation
mirror of https://github.com/cncf/foundation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add links to attribution recommendations 

Signed-off-by: Steve Winslow <steve@swinslow.net>
This commit is contained in:
Steve Winslow 2023-10-18 17:16:41 -04:00
parent 9eff84de41
commit 0c69dcc8d5
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
copyright-notices.md
View File

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

4
license-notices.md
View File

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