Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5134
@greghogan That may or may not be possible, not 100% sure. Re-distributing
it does certainly not work.
To my current understanding, the Apache guidelines say we would need to
make sure that downstream consumers of Flink (also the source) don't
accidentally pull in a GPL license. For weak copyleft, where consuming it only
via linking, it is okay, but for strong copyleft, where accidentally linking it
results in copyleft, I think the hurdles for that are pretty high. There are
some gray zone areas (like MPL) where the understanding is that "optional"
dependency is okay because it requires an explicit action by a downstream user
(re-adding the dependency) and the potential damage is not too high.
I have seen a lot of cases first hand in the past months how many companies
that want to use open source freak out as soon as they see an instance of GPL.
We would make Flink's adoption easier if we did not have that.
My first suggestion would be to consolidate this in a separate
`flink-benchmarks` repository. That would also keep the core Flink repository
"clear" of GPL. I could check with Apache legal for a final answer.
---
