You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by ba...@apache.org on 2019/03/24 23:53:15 UTC
svn commit: r1856167 -
/infrastructure/site/trunk/content/legal/resolved.mdtext
Author: bayard
Date: Sun Mar 24 23:53:15 2019
New Revision: 1856167
URL: http://svn.apache.org/viewvc?rev=1856167&view=rev
Log:
Using three deep for better l&f :(
Modified:
infrastructure/site/trunk/content/legal/resolved.mdtext
Modified: infrastructure/site/trunk/content/legal/resolved.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/legal/resolved.mdtext?rev=1856167&r1=1856166&r2=1856167&view=diff
==============================================================================
--- infrastructure/site/trunk/content/legal/resolved.mdtext (original)
+++ infrastructure/site/trunk/content/legal/resolved.mdtext Sun Mar 24 23:53:15 2019
@@ -90,7 +90,7 @@ For the purposes of being included in an
Many of these licenses have specific attribution terms that need to be adhered to, often by [adding
them to the NOTICE file](/dev/licensing-howto.html). Ensure you are doing this when including these works.
-## Handling Public Domain 'licensed' works
+### Handling Public Domain 'licensed' works
Works in the public domain (or covered by a license treated similarly) may be included within Apache products. Attribution is required (in a similar fashion to the Category A list.
@@ -117,7 +117,7 @@ Determining whether the copyright in a w
For the purposes of being included in an Apache Software Foundation product, licenses and/or projects described in this section may be included **IF** specified conditions are met.
-## Appropriately Labelled Condition
+### Appropriately Labelled Condition
In all Category B cases our users should not be surprised at their inclusion in our products.
By attaching an appropriate and prominent label to the distribution
users are less likely to be unaware of restrictions significantly
@@ -127,11 +127,11 @@ distribution - for example in a README,
its licensing, and a url to the its homepage. Please also ensure to comply with
any attribution/notice requirements in the specific license in question.
-## Binary-only Inclusion Condition
+### Binary-only Inclusion Condition
Unless otherwise specified, all Category B licensed works should be included in
binary-only form in Apache Software Foundation convenience binaries (and not source code).
-## "Weak Copyleft" Licenses
+### "Weak Copyleft" Licenses
Each license in this section requires some degree of reciprocity. This may mean that
additional action is warranted in order to minimize the chance that a user of
@@ -170,12 +170,12 @@ standard), inclusion of appropriately la
permitted. An example of this is the web-facesconfig_1_0.dtd, whose
inclusion is mandated by the JSR 127: JavaServer Faces specification.
-## Including Creative Commons Attribution content ## {#cc-by}
+### Including Creative Commons Attribution content ## {#cc-by}
Works under the [Creative Commons Attribution (CC-BY)](http://creativecommons.org/licenses/by/4.0/) licenses (2.5, 3.0, and 4.0)
contain terms related to "Effective Technological Measures", which may come as a surprise to users. Thus their inclusion
shall be appropriately labelled and only in binary form.
-## Unmodified media under the Creative Commons Attribution-Share Alike license ## {#cc-sa}
+### Unmodified media under the Creative Commons Attribution-Share Alike license ## {#cc-sa}
Unmodified media under the
[Creative Commons Attribution-Share Alike 2.5](http://creativecommons.org/licenses/by-sa/2.5/),
@@ -185,7 +185,7 @@ LICENSE/NOTICE/README changes. For any o
Note that media is intended to mean binary visual/video/audio elements used in our documentation. It is not intended to mean inclusion inside our source code.
-## Doug Lea's concurrent library ## {#concurrent}
+### Doug Lea's concurrent library ## {#concurrent}
Doug Lea's concurrent library is public domain, but contains some Sun files which are not public domain. This may
be included in ASF products much like the 'weak copyleft' list above.
@@ -194,17 +194,17 @@ is appropriately labeled". If using
treat as Category A (or get the files from
[Harmony](http://svn.apache.org/repos/asf/harmony/standard/classlib/trunk/modules/concurrent/src/main/java/java/util/concurrent/)).
-## Adding OSGi metadata to weak copyleft binaries ## {#osgi-category-b}
+### Adding OSGi metadata to weak copyleft binaries ## {#osgi-category-b}
Insertion of OSGi metadata into 'Category B' licensed jars is
permitted providing that a note that this has occurred is included in the
prominent labeling for the jar.
-## Cobertura reports ## {#cobertura}
+### Cobertura reports ## {#cobertura}
Cobertura reports may be included in ASF distributions.
-## Handling licenses that prevent modification ## {#no-modification}
+### Handling licenses that prevent modification ## {#no-modification}
There are licenses that give broad rights for redistribution of
**unmodified** copies. Such licenses are not open source, but they
@@ -224,7 +224,7 @@ Material under the following licenses ma
[Additional License](http://www.day.com/maven/jsr170/jars/LICENSE.txt))
- [WSDL (2004) Schema Files License](https://issues.apache.org/jira/browse/LEGAL-385)
-## Incuding build tools in ASF products ## {#build-tools}
+### Incuding build tools in ASF products ## {#build-tools}
Many languages have developed an ecosystem of associated tools that aid
in the building of artifacts for distribution. While such tools may not
@@ -251,17 +251,17 @@ To date, the following tools have been a
- [OCamlMakefile](http://hg.ocaml.info/release/ocaml-make/)
- [setup.rb](http://i.loveruby.net/en/projects/setup/)
-## Including Perl licensed header files when creating dynamically loaded XS modules
+### Including Perl licensed header files when creating dynamically loaded XS modules
Developing Perl bindings which link compiled C code to create dynamically loaded XS modules requires including header files licensed under the Perl license (http://dev.perl.org/licenses/ - GPL-any/Artistic1, with exceptions).
You may include these header files - XSUB.h, perl.h and EXTERN.h (see: [LEGAL-79](https://issues.apache.org/jira/browse/LEGAL-79)).
-## Including Doxygen-generated config files
+### Including Doxygen-generated config files
As long as the generated comments are removed from the Doxygen-generated files, these files may be used.
-## Can Apache projects have external dependencies on Ruby licensed works? ## {#ruby-license}
+### Can Apache projects have external dependencies on Ruby licensed works? ## {#ruby-license}
A project written primarily and obviously in Ruby can have a dependency either on Matz's Ruby Interpreter (MRI),
or on any Gem which is licensed under the [Ruby license](http://www.ruby-lang.org/en/LICENSE.txt).
@@ -331,14 +331,14 @@ JSON license
[list of alternatives](https://wiki.debian.org/qa.debian.org/jsonevil).
-## They may not be distributed ## {#prohibited}
+### They may not be distributed ## {#prohibited}
Apache projects may not distribute Category X licensed components, be it in source or binary form;
and be it in ASF source code or convenience binaries. As with the previous question on platforms,
the component can be relied on if the component's license terms do not affect the Apache product's
licensing. For example, using a GPL'ed tool during the build is OK, however including GPL'ed source code is not.
-## They may be relied upon when they support an optional feature ## {#optional}
+### They may be relied upon when they support an optional feature ## {#optional}
Apache projects can rely on components under prohibited licenses if the component is only needed
for optional features. When doing so, a project shall provide the user with instructions on how
@@ -351,7 +351,7 @@ ask yourself in this situation is:
# FAQ:
-## Does it matter what platform an Apache product is created to work with? ## {#platform}
+### Does it matter what platform an Apache product is created to work with? ## {#platform}
It does not matter, unless the terms for that platform affect
the Apache product's licensing. For example, creating a product that
@@ -365,14 +365,14 @@ depend on the licensing of said code. Al
of the platform would affect the Apache code, we recommend that you check the legal-discuss@
archives to see if it has come up before, and if not email legal-discuss@ to find out.
-## Is IP clearance required for library dependencies? {#library-ip-clearance}
+### Is IP clearance required for library dependencies? {#library-ip-clearance}
No.
[IP clearance](http://incubator.apache.org/ip-clearance/index.html)
is used to import code bases from outside Apache for future development here.
-## How should works for which multiple mutually exclusive licenses are available be handled? ## {#mutually-exclusive}
+### How should works for which multiple mutually exclusive licenses are available be handled? ## {#mutually-exclusive}
When including that work's licensing, state which license is
being used and include only the license that you have chosen. Prefer
@@ -381,7 +381,7 @@ work itself if, for example, it mentions
in the source headers.
-##What Are Required Third-party Notices?## {#required-third-party-notices}
+### What Are Required Third-party Notices? ## {#required-third-party-notices}
When a release contains third party works, the licenses covering those works may ask that consumers are informed
in certain specific fashions. These *third party notices* vary from license to license. Apache releases should contain a copy of each license, usually contained in the LICENSE document. For many licenses this is a sufficient notice. For some licenses some additional notice is required. In many cases, this will be included within the dependent artifact.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org