www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-437) Optional GPL dependencies in Docker images
Date Sun, 10 Feb 2019 21:07:00 GMT

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

Henri Yandell commented on LEGAL-437:

I don't see an issue with aggregation of an optional dependency that must be actively turned
on, and where the individual turning it on is clearly aware of the licensing.

> Optional GPL dependencies in Docker images
> ------------------------------------------
>                 Key: LEGAL-437
>                 URL: https://issues.apache.org/jira/browse/LEGAL-437
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Gian Merlino
>            Priority: Major
> Infra offers automated pushes of images to Docker Hub (https://hub.docker.com/u/apache/).
As we are looking into setting this up with Apache Druid, a question came up about our optional
MySQL dependency (Derby and PostgreSQL are other options). Would it be okay to include the
connector jar in a Docker image published on Docker Hub, if it is in an extension that is
not enabled by default, and is clearly marked?
> An argument was raised on the Druid dev list that it should be, since this form of distribution
appears to be "mere aggregation" similar to inclusion of GPL licensed programs like bash,
cp, ls, and others, which are common on published Docker images for other ASF projects. But
we want to double-check.

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