Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Message-ID: <2026899650.1261257441195.JavaMail.jira@brutus>
Date: Sat, 19 Dec 2009 21:17:21 +0000 (UTC)
From: "Ralph Goers (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Subject: [jira] Commented: (LEGAL-54) Resolved.html should discuss optional
 dependencies.
In-Reply-To: <116945043.1247867834796.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ralph Goers commented on LEGAL-54:
----------------------------------

Again, I disagree. The long history was in saying category X licenses couldn't be used at all. It is only fairly recently that the discussion and approval of using LGPL'd works in optional dependencies has come up and been approved. A good question for you is "Under what circumstances would you consider an optional dependency on an LGPL'd work to not be OK"? Since the LGPL is triggered by distribution I cannot think of any.  Requiring everyone to have to come to legal-discuss or open a new Jira issue for each LGPL'd work seems pointless if the answer will always be the same.

> Resolved.html should discuss optional dependencies.
> ---------------------------------------------------
>
>                 Key: LEGAL-54
>                 URL: https://issues.apache.org/jira/browse/LEGAL-54
>             Project: Legal Discuss
>          Issue Type: Task
>            Reporter: Ralph Goers
>
> I recommend something like the following.
> Change the answer to "Which licenses may NOT be included within Apache products?"
> Apache products may not require components under the following licenses. 
> ...
> Q. Can Apache projects use components under prohibited licenses for optional use?
> Apache project must not distribute works under a prohibited licensed or require a work under a prohibited license
> to perform functions essential to normaloperation. However, projects may use LGPL licensed works in optional
> features that are not enabled by default. 
> Apache projects may also use components under a prohibited license as part of the project's build process or on their web site where they meet all the legal obligations of the license.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org