linghengqian commented on issue #507: URL: https://github.com/apache/flagon-useralejs/issues/507#issuecomment-2408831885
> migrate the examples to newer version of ELK stack which are AGPL, but remove examples from the release zip/tar (these currently get sucked in which is a no-no, even if there aren't any AGPL dependencies in the NPM package or src). - Does this mean that `apache/flagon-useralejs` needs to maintain downstream Docker Images for ElasticSearch and Kibana? Even though these Docker Images are actually AGPL LICENSE which is not approved by ASF? Docker images of ElasticSearch and Kibana made by Elastic will still be under the Elastic V2 LICENSE. This has been clarified at https://discuss.elastic.co/t/elasticsearch-binaries-and-images-be-coverd-by-the-agpl-license/367084/4?u=linghengqian . - But from my point of view, the source code of the Dockerfile or other build scripts that generate the AGPL LICENSE Docker Image can still be any LICENSE, regardless of the AGPL. I don't see https://github.com/apache/flagon-useralejs/tree/master/example redistributing Elastic's files. - This involves another topic. Since Linux with GPL V2 LICENSE is usually used in Docker Image, Docker Hub is just a downstream distribution channel of ASF. Using ElasticSearch in an ASF project is much more troublesome than using OpenSearch in an ASF project. -- 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
