www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-280) Can java based projects broadly have optional modules with Cat X dependencies?
Date Wed, 25 Jan 2017 04:04:26 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837150#comment-15837150
] 

John D. Ament commented on LEGAL-280:
-------------------------------------

I've not committed it yet, here's the change.

{code}
Index: content/legal/resolved.mdtext
===================================================================
--- content/legal/resolved.mdtext	(revision 1780133)
+++ content/legal/resolved.mdtext	(working copy)
@@ -249,15 +249,15 @@
 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.
 
-## Can Apache projects rely on components under prohibited licenses? ## {#prohibited}
+## Can Apache projects distribute components under prohibited licenses? ## {#prohibited}
 
-Apache projects cannot distribute any such components.
-As with the previous question on platforms, the component can be relied on if the component's
licence terms do not affect the Apache product's licensing.
-For example, using a GPL'ed tool during the build is OK.
+Apache projects cannot distribute any such components.  This means that no source code can
be from [Category X](#category-x) and that any convenience binaries produced may not include
such contents.
+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.
 
-## Can Apache projects rely on components whose licensing affects the Apache product? ##
{#optional}
+## Can Apache projects rely on components under prohibited licenses? ## {#optional}
 
-Apache projects cannot distribute any such components.
+Apache projects cannot distribute any such components within their releases.
 However, if the component is only needed for optional features, a project can provide the
user with instructions on how
 to obtain and install the non-included work. Optional means that the component is not required
for
 standard use of the product or for the product to achieve a desirable level of quality. The
question to

{code}

Basically, rephrase the questions as you recommended, but also added a note explicitly calling
out what is intended to be excluded.

> Can java based projects broadly have optional modules with Cat X dependencies?
> ------------------------------------------------------------------------------
>
>                 Key: LEGAL-280
>                 URL: https://issues.apache.org/jira/browse/LEGAL-280
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: John D. Ament
>
> This is a follow up to https://issues.apache.org/jira/browse/LEGAL-198 where we introduce
that Amazon License is OK if its an optional dependency.
> Does this apply to anything in Cat-X or specifically to those under field of use restrictions
or specifically to the Amazon License?
> This probably is limited to java/jvm projects, where its an optional feature (e.g. the
library still works without it or has an alternative that can be dropped in instead) that
is included in a convenience binary.  To build the optional module from source, you would
need to have the LGPL library available locally in binary form (I would imagine).
> - Java projects like this are not directly distributing the LGPL dependency
> - They may use build tools, or provide other such means, to download these software (e.g.
its clear to the user)
> - Its dynamically linked, by definition.  E.g. we wouldn't produce an "uber jar" or anything
that in some way bundled the extra dependency in a way that was non-obvious to the user
> - I'm assuming this precludes modifications to the 3rd party library, since those couldn't
be licensed under ALv2



--
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


Mime
View raw message