[jira] [Commented] (LEGAL-192) Why is LGPL not allowed

["Shane Curcuru (JIRA)" <ji...@apache.org>]

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

Shane Curcuru commented on LEGAL-192:
-------------------------------------

To clarify Henri's closing comment about LGPL downloading, I'd like to include a reference here in this JIRA for future readers.  The current ASF policy link:

  https://www.apache.org/legal/resolved.html#optional

Currently states:
--------
CAN APACHE PROJECTS RELY ON COMPONENTS WHOSE LICENSING AFFECTS THE APACHE PRODUCT?

Apache projects cannot distribute any such components. 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 ask yourself in this situation is:

"Will the majority of users want to use my product without adding the optional components?"
--------

> Why is LGPL not allowed
> -----------------------
>
>                 Key: LEGAL-192
>                 URL: https://issues.apache.org/jira/browse/LEGAL-192
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sam Halliday
>
> According to http://www.apache.org/legal/resolved.html the LGPL is not allowed because
>   "The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion. Therefore, LGPL-licensed works must not be included in Apache products."
> where part three is
>   "The license must not place restrictions on the distribution of larger works, other than to require that the covered component still complies with the conditions of its license."
> But I see no conflict here with regard to distribution. The license clearly states that software which uses LGPL software can be distributed under whatever license the developer wishes:
>   http://www.gnu.org/licenses/lgpl-2.1.html
> The LGPL does, however, require that any changes to the LGPL component is released as LGPL (including source code).
> I have an LGPL library and there is a desire to see it included in an Apache project. Since my project places no constraint on the distribution of the larger work, I do not see why I should have to change the license in order to comply with these rules.
> If I was using the GPL, I would see your point. But this is the LGPL and it appears to meet your objectives.



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