www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-228) Optional Java Use for Essential Functionality
Date Thu, 15 Oct 2015 19:04:05 GMT

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

Dennis E. Hamilton commented on LEGAL-228:

That makes sense to me when the project produces a Java application.  AOO is a native application
(mainly in C++) and that is what is startling about this optionality.

I suppose we could declare that Java is required for full functionality, and explain how to
get one that works, if one on the platform, if any, doesn't.

> Optional Java Use for Essential Functionality
> ---------------------------------------------
>                 Key: LEGAL-228
>                 URL: https://issues.apache.org/jira/browse/LEGAL-228
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Dennis E. Hamilton
> This may not be a legal question but a practice question.
> At <http://www.apache.org/legal/resolved.html#optional>, the use of an optional
dependency is explained with regard to the quality of the result when the option is not exercised.
> "[I]f 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?'
> In the specific case of Apache OpenOffice, the Java JRE is not distributed and it is
not necessarily found on the platform in the form that AOO requires to exercise its optional
dependencies on Java.  I don't know whether redistributing a JRE is inappropriate, although
I would think so. 
> The key facet is that there are *essential* functionalities that are only available if
a suitable JRE is present.  Users only discover that essentiality by failures that arise when
attempting to exercise certain functions.
> Granting that the usability and awareness of what requires a JRE could be handled better,
does this dependency in AOO fall under this provision of the legal FAQ?

This message was sent by Atlassian JIRA

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

View raw message