You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Justin Mclean (JIRA)" <ji...@apache.org> on 2018/01/26 09:52:00 UTC

[jira] [Commented] (LEGAL-362) Supposed GPLv3 non-derivative work in sub-sub-dependency Apache Airflow

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

Justin Mclean commented on LEGAL-362:
-------------------------------------

IANAL but looks like existing ASF policy would consider it a derivative work.  See [https://www.apache.org/licenses/GPL-compatibility.html] where it states:
"We avoid GPLv3 software because merely linking to it is considered by the GPLv3 authors to create a derivative work." and "This is an identical issue for both GPLv2 and GPLv3."

> Supposed GPLv3 non-derivative work in sub-sub-dependency Apache Airflow
> -----------------------------------------------------------------------
>
>                 Key: LEGAL-362
>                 URL: https://issues.apache.org/jira/browse/LEGAL-362
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Bolke de Bruin
>            Priority: Major
>
> Hello,
> Apache Airflow (incubating) is dependent on python-nvd3 (BSD) > python-slugify (MIT) > unidecode (GPLv2 and later) by means of importing python-nvd3 as a module. We were made aware of this in AIRFLOW-1430 .--
> As 'unidecode' is a derivative work of a Perl module that was dual licensed Perl Artistic and GPLv2 and later, I initially asked the author to consider dual licensing again. This was [denied|https://github.com/avian2/unidecode/issues/23#issuecomment-360242600].
> Reaching out to the authors of python-slugify I asked them to consider basing on an alternative module citing their MIT license might be in violation of the GPLv2+ licensed module. Again this was denied, [citing|https://github.com/un33k/python-slugify/issues/50#issuecomment-360258528] that they did not consider themselves derivative work of unidecode.
> I reached out again to the author of unidecode, asking if he agrees with the views of the authors of python-slugify. He [does|https://github.com/avian2/unidecode/issues/23#issuecomment-360242600].
> So, I'm inclined to argue that given the author of unidecode does not consider python-slugify is a derivative work of his own work that there is no license violation, but I wonder what your views are.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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