www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-285) Question re: using dual-licensed JavaScript plugin in blog site for Impala (incubating)
Date Wed, 11 Jan 2017 01:38:58 GMT

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

Justin Mclean commented on LEGAL-285:

IMO yes see [1] you can just select the MIT license. Given that your probably not bundling
this in a release it probably doesn't matter.
1. https://www.apache.org/legal/resolved#mutually-exclusive

> Question re: using dual-licensed JavaScript plugin in blog site for Impala (incubating)
> ---------------------------------------------------------------------------------------
>                 Key: LEGAL-285
>                 URL: https://issues.apache.org/jira/browse/LEGAL-285
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: David Knupp
> Hopefully this is an appropriate place to get help on this issue.
> We are setting up a development blog for the Impala (incubating) project. The static
site generator we are using is MIT-licensed, but we have found one of the supporting JavaScript
files is dual-licensed: MIT/GPL2.
> According to the licenses text on the source repo:
> "This software is licensed under a dual license system (MIT or GPL version 2). This means
you are free to choose with which of both licenses (MIT or GPL version 2) you want to use
this library."
> https://github.com/aFarkas/html5shiv/blob/master/MIT%20and%20GPL2%20licenses.md
> Would the use of this file be compatible with the Apache License? Are we permitted to
include it for the purposes of running our development blog?

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