linghengqian commented on issue #507: URL: https://github.com/apache/flagon-useralejs/issues/507#issuecomment-2411641217
> *Is that a problem?* - This is not a problem because end users download the Elastic V2 LICENSE binaries from Docker Hub, and those binaries are not part of the source code at https://github.com/apache/flagon/tree/master/docker . - I believe the source code of https://github.com/apache/flagon/tree/master/docker will still be Apache V2, and this will not change due to any business decision of Elastic. https://github.com/apache/flagon/tree/master/docker just uses the Docker Image made by Elastic during the demonstration. It is very common to use the Apache V2 LICENSE Dockerfile to describe the installation process of the GPL V3 LICENSE Docker Image. This is no different from the treatment of apache skywalking in https://github.com/apache/skywalking-showcase and https://github.com/apache/skywalking . Of course, skywalking does not need elasticsearch to run. It’s just that in the skywalking community, most people use elasticsearch as data storage. - When the final downstream user downloads the `.tar.gz` of https://github.com/apache/flagon from https://downloads.apache.org/ , the Docker Image is obviously not included. The user downloads the Docker Image from Docker Hub, which is not an official distribution channel of ASF at all. It is just a downstream distribution channel, and the LICENSE is handled quite freely. It is normal for Docker Images to contain proprietary software. If the LICENSE of all layers of a Docker Image really needs to be discussed, it will become very complicated. For example, the long article at https://www.linuxfoundation.org/resources/publications/docker-containers-what-are-the-open-source-licensing-considerations . - There is almost no need to consider Elastic V2 LICENSE, unless Apache Flagon must depend on Elasticsearch. Or Apache Flagon publishes an npm package that uses the https://github.com/elastic/eui npm package of Elastic V2 LICENSE. But if I remember correctly, npm is also not an official distribution channel of ASF. - When we talk about the official distribution channels of ASF, it is either https://repository.apache.org/ or https://downloads.apache.org/ . Other distribution channels not managed by ASF are actually not related to ASF, but sometimes ASF Infra helps maintain the accounts of these downstream channels. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@flagon.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@flagon.apache.org For additional commands, e-mail: notifications-h...@flagon.apache.org
