Hi, The authoritative source is here: https://www.apache.org/legal/resolved.html
If no conflicting licensed code is actually bundled (or released in source or binary form), it isn’t an problem. The docker compose file itself would be ASLv2, but since we not ship any category x license code ourselves, it shouldn’t be an issue. Gruß Richard > Am 22.05.2026 um 14:16 schrieb Gianluca Graziadei > <[email protected]>: > > Hi, > I am preparing a PR https://github.com/apache/storm/pull/8706 to introduce > a repeatable, "laptop-friendly" distributed Storm cluster via Docker > Compose, designed to improve local development and benchmarking by forcing > true intra-cluster serialization and Netty network communication. > > The environment includes a network simulator (netsim.sh) using tc/netem to > realistically test back-pressure under controlled latency and jitter, as > well as a full observability stack featuring Prometheus and Grafana 11.1 > provisioned with custom, dashboard JSONs built from scratch. Before moving > this PR out of draft, I would appreciate your feedback regarding ASF > compliance: while Grafana OSS 11.1 is under the AGPLv3 license, it is > strictly confined to local dev-tools at runtime via a Docker image > reference, meaning no AGPLv3 code is ever bundled or distributed with Storm. > > Please let me know your thoughts on this approach and if including this > runtime image reference in the dev-tools Compose file is acceptable, or if > I should explore alternatives like Apache Superset.
