You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2015/03/28 23:05:52 UTC
[jira] [Closed] (LEGAL-109) [POLICY] Resolve "Unmodifiable
Standards" Exception
[ https://issues.apache.org/jira/browse/LEGAL-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed LEGAL-109.
-------------------------------
Resolution: Won't Fix
> [POLICY] Resolve "Unmodifiable Standards" Exception
> ----------------------------------------------------
>
> Key: LEGAL-109
> URL: https://issues.apache.org/jira/browse/LEGAL-109
> Project: Legal Discuss
> Issue Type: Task
> Reporter: Robert Burrell Donkin
> Assignee: Robert Burrell Donkin
>
> ATM in "Previously Asked Questions"[1] (see below) an exception for small source documents unlikely to be modified is included in the weak-copyleft section but is missing from the no-modifications. I'm not clear that this was intentional, and understand that - in practice - projects already use the exception for reasonable licenses which do not allow modification.
> I think it would be clearer to introduce a new category (category-s) which applies an exception to both weak-copyleft licenses and some no-modification licenses used by some standards bodies.
> -------------------------------------------
> How should so-called "Weak Copyleft" Licenses be handled?
> ...
> For small amounts of source that is directly consumed by the ASF product at runtime
> in source form, and for which that source is unmodified and unlikely to be changed
> anyway (say, by virtue of being specified by a standard), inclusion of appropriately labeled
> source is also permitted. An example of this is the web-facesconfig_1_0.dtd, whose
> inclusion is mandated by the JSR 127: JavaServer Faces specification.
> <snip>
> How should licenses that prevent modification be handled?[3]
> There are licenses that give broad rights for redistribution of unmodified copies.
> Such licenses are not open source, but they do satisfy the second and third
> guiding principles above.
> Apache projects must not include material under such licenses in version control
> or in released source packages. It is however acceptable for a build process to
> automatically download such non-software materials like fonts and standardized data
> and include them in the resulting binaries. Such use makes it clear that these
> dependencies are not a part of the open source code of the project.
> -------------------------------------------
> [1] http://www.apache.org/legal/resolved.html
> [2] http://www.apache.org/legal/resolved.html#category-b
> [3] http://www.apache.org/legal/resolved.html#no-modification
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org