summaryrefslogtreecommitdiff
path: root/github-management
diff options
context:
space:
mode:
authorSteve Winslow <swinslow@gmail.com>2019-03-23 08:43:21 -0400
committerSteve Winslow <swinslow@gmail.com>2019-03-23 09:04:10 -0400
commitc383ee21baab864e82ac01f3571735e850745d11 (patch)
tree874125f471536b7dea9bd3786c208db9b32f73c7 /github-management
parentfe7527890216e13d4d0d6eba7df1395215de4ba0 (diff)
Add clarifying details about copyright notices
Signed-off-by: Steve Winslow <swinslow@gmail.com>
Diffstat (limited to 'github-management')
-rw-r--r--github-management/kubernetes-repositories.md23
1 files changed, 21 insertions, 2 deletions
diff --git a/github-management/kubernetes-repositories.md b/github-management/kubernetes-repositories.md
index e9e3c731..87240c7a 100644
--- a/github-management/kubernetes-repositories.md
+++ b/github-management/kubernetes-repositories.md
@@ -98,8 +98,13 @@ the developers who could not be reached
[@caniszczyk](https://github.com/caniszczyk) for review of third party deps
* Boilerplate text across all files should attribute copyright as follows:
`"Copyright <Project Authors>"` if no CLA was in place prior to donation
- * If there was a CLA prior to donation, the copyright can be updated post-transfer.
- The copyright _must_ be updated by someone from the donating organization.
+ * Additions of [the standard Kubernetes header](https://github.com/kubernetes/kubernetes/blob/master/hack/boilerplate/boilerplate.go.txt)
+ to code created by the contributors can occur post-transfer, but should
+ ideally occur shortly thereafter.
+
+Note that copyright notices should only be modified or removed by the people or
+organizations named in the notice. See [the FAQ below](#faq) for more information
+regarding copyrights and copyright notices.
## Core Repositories
@@ -222,6 +227,20 @@ associated projects. Many things seem vague. Help!**
True, we need to improve these things. For now, do the best you can to conform
to the spirit of the proposal (e.g. post the code of conduct, etc)
+**When I donate my project, am I transferring my copyrights?**
+
+No. All contributors retain ownership of their copyrights in the code they donate.
+Instead, they are granting a license to the project (that's the 'L' in 'CLA').
+
+For consistency and efficiency in complying with notice requirements, code that is
+donated to a Kubernetes repo should use [the standard header](https://github.com/kubernetes/kubernetes/blob/master/hack/boilerplate/boilerplate.go.txt)
+referencing "The Kubernetes Authors". That doesn't mean you are transferring your
+copyright. Instead, it's a general reference to the fact that the copyrights remain
+owned by the authors of Kubernetes.
+
+Note that you should _never_ modify or remove a third party's copyright notice if
+you are not authorized by them to do so.
+
[GitHub's archive feature]:
https://help.github.com/articles/archiving-a-github-repository/
[kubernetes-retired]: https://github.com/kubernetes-retired