You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Henri Yandell (Jira)" <ji...@apache.org> on 2019/09/02 02:46:00 UTC
[jira] [Commented] (LEGAL-437) Optional GPL dependencies in Docker
images
[ https://issues.apache.org/jira/browse/LEGAL-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920578#comment-16920578 ]
Henri Yandell commented on LEGAL-437:
-------------------------------------
We should comply with the byteman licensing. We should provide the source code for byteman in the published apache/hadoop-runner Docker image.
> Optional GPL dependencies in Docker images
> ------------------------------------------
>
> Key: LEGAL-437
> URL: https://issues.apache.org/jira/browse/LEGAL-437
> Project: Legal Discuss
> Issue Type: Question
> Components: Policy 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org