The lists below declare which licenses are authorized and which licenses are
excluded from applying to any part of a product distributed by an ASF PMC. Categorized lists of licenses
are used in this policy to address the third guiding principle of this policy.
NOTE: Licenses not appearing on these lists must be explicitly approved by the ASF Legal Affairs
officer prior to distribution. License approval requests may be sent to the legal-discuss mailing list.
NOTE: Some licenses listed below do not include version numbers, in which case the
specific version referred to is the one posted on the OSI site.
Third-party works, in both source and binary form,
may be included within Apache products when made available under the following licenses:
Each license in this category requires some degree of reciprocity; therefore, additional action must be taken in order
to minimize the chance that a user of an Apache product
will create a derivative work of a reciprocally-licensed portion of an Apache product without being aware of the applicable
The first action that must be taken is that software under the following licenses may only be included within an Apache product if the inclusion is appropriately labeled:
For small amounts of source that is directly consumed by the ASF product
at runtime in source form, and for which that source is unlikely to be changed
anyway (say, by virtue of being specified by a standard), this action is
sufficient. An example of this is the web-facesconfig_1_0.dtd, whose inclusion is mandated by the JSR 127: JavaServer Faces specification.
Code that is more substantial, more volatile, or not directly consumed at
runtime in source form may only be distributed in binary form.
By including only the object/binary form, there is less exposed surface area of the third-party work from
which a work might be derived; this addresses the second guiding principle of this policy.
By attaching a prominent label to the distribution and requiring an explicit action by the user to get the
reciprocally-licensed source, users are less likely to be unaware of restrictions significantly different from those
of the Apache License; this addresses the fourth guiding principle of this policy.
Although the source must not be included in Apache products, the NOTICE file, which is required to be included
in each ASF distribution, must point to the source form of the included binary
(more on that in the forthcoming "Receiving and Releasing Contributions" document).
Note that works written in a scripting language without a binary form
cannot be included in any ASF product under one of these licenses (see
Transition and Exceptions). In addition, C-based projects may have difficulty using works under these licenses since
they would have to deal with platform-specific binaries, rather than just
distributing source that can be built on most any platform.
The following licenses must not apply to any software within an Apache product,
whether in source or binary form. See Options for Prohibited
Works for applicability to system requirements or
optional works distributed elsewhere.
* see discussion of this in Transition and Exceptions