svn commit: r1806521 - /infrastructure/site/trunk/content/licenses/index.mdtext

[cl...@apache.org]

Author: clr
Date: Tue Aug 29 00:49:52 2017
New Revision: 1806521

URL: http://svn.apache.org/viewvc?rev=1806521&view=rev
Log:
Add Provenance section to Licenses

Modified:
    infrastructure/site/trunk/content/licenses/index.mdtext

Modified: infrastructure/site/trunk/content/licenses/index.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/licenses/index.mdtext?rev=1806521&r1=1806520&r2=1806521&view=diff
==============================================================================
--- infrastructure/site/trunk/content/licenses/index.mdtext (original)
+++ infrastructure/site/trunk/content/licenses/index.mdtext Tue Aug 29 00:49:52 2017
@@ -169,6 +169,40 @@ or digitally signing via gpg. Unsigned d
 From wikipedia.com: A signature is a handwritten (and often stylized) depiction of someone's name
 or nickname, on documents as a proof of identity and intent. 
 
+# Provenance # {#provenance}
+
+Source code (including machine-readable documentation, release notes, guides,
+test cases, run books, and scripts) in Apache repositories falls into three
+classifications (solely for the purpose of this discussion):
+
+#### Code developed at Apache under Apache governance, licensed to Apache by its developers under a Contributor License Agreement, distributed by Apache, and licensed to downstream users under the Apache license
+
+This represents most code at Apache. The code contains a standard Apache license 
+header which refers to the standard Apache license in the distribution.
+
+#### Code developed elsewhere, licensed to Apache under a Software Grant Agreement, incorporated into Apache projects, distributed by Apache, and licensed to downstream users under the Apache license
+
+This is code that is being brought into Apache for future development as part 
+of an Apache project. The headers on all files are changed to the standard Apache 
+header. Most incubator projects start as externally-developed code and the 
+Intellectual Property Clearance process is done as part of incubation. 
+
+Code that is originally developed elsewhere and is being brought into Apache for 
+future development as part of an existing project must have the Intellectual Property 
+Clearance process done explicitly by the PMC of the receiving project, under the 
+auspices of the Incubator PMC which must approve the process. 
+
+#### Code developed elsewhere, received under a Category A license, incorporated into Apache projects, distributed by Apache, and licensed to downstream users under its original license
+
+This code retains its external identity and is being incorporated into an Apache project 
+for convenience, to avoid referencing an external repository whose contents are not 
+under control of the project. The code retains its original license; and distribution as 
+part of the Apache project explicitly calls out the license. The code retains its original 
+header which refers to its own license in the distribution. If changes are made to the 
+code while at Apache, the standard Apache header is prepended to each changed 
+file. Additionally, any legally-required notices related to the code are published in the 
+distribution.
+
 # Export restrictions # {#crypto}
 
 For export restriction information, please consult our [ASF Export
@@ -182,4 +216,5 @@ Trademark Use Policy](/foundation/marks/
 # Questions? # {#questions}
 
 For answers to frequently asked licensing questions, please consult our 
-[Licensing Frequently Asked Questions](/foundation/license-faq.html) page.
\ No newline at end of file
+[Licensing Frequently Asked Questions](/foundation/license-faq.html) page.
+



---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org