From 305915b8f6613b706aaba3c954e962746e62a0e0 Mon Sep 17 00:00:00 2001
From: Chris Lattner
Date: Tue, 20 May 2008 20:06:53 +0000
Subject: [PATCH] Clarify copyright transfer when you don't own the copyright
of the contributed code.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51329 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/DeveloperPolicy.html | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 18c1ff34ac2..ab985b565b9 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -458,7 +458,7 @@ Changes
Although UIUC may eventually reassign the copyright of the software to another
- entity (e.g. a dedicated non-profit "LLVM Organization", or something)
+ entity (e.g. a dedicated non-profit "LLVM Organization")
the intent for the project is to always have a single entity hold the
copyrights to LLVM at any given time.
@@ -467,6 +467,12 @@ Changes
reduces the managerial burden for any kind of administrative or technical
decisions about LLVM. The goal of the LLVM project is to always keep the code
open and licensed under a very liberal license.
+
+ When contributing code, you also affirm that you are legally entitled to
+ grant this copyright, personally or on behalf of your employer. If the code
+ belongs to some other entity, please raise this issue with the oversight
+ group before the code is committed.
+
@@ -480,7 +486,8 @@ Changes
- You can freely distribute LLVM.
- You must retain the copyright notice if you redistribute LLVM.
- - Binaries derived from LLVM must reproduce the copyright notice.
+ - Binaries derived from LLVM must reproduce the copyright notice (e.g.
+ in an included readme file).
- You can't use our names to promote your LLVM derived products.
- There's no warranty on LLVM at all.