The modifications to the H2 source would need to be published under "MPL-2.0", "EPL-1.0", or "(MPL-2.0 OR EPL-1.0)". I don't believe there would be interest in publishing ASF-community authored source under a different license than Apache 2.0.
Hen On Tue, Jul 9, 2019 at 12:50 PM Denis Magda <dma...@apache.org> wrote: > Adding a valid legal mailing list. > > - > Denis > > > On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <dma...@apache.org> wrote: > >> Apache Ignite's SQL engine is tightly coupled with the H2 database engine >> [1] that provides basic parsing and query execution capabilities. >> >> H2 is licensed under dual MPL 2.0 and EPL 1.0 [2], thus Ignite community >> uses H2 binary artifacts for the development needs and doesn't have H2 >> source code in Ignite codebase. >> >> However, these days Ignite SQL needs to go beyond H2 capabilities and >> we're planning to fork H2 and produce H2 binaries from there for Ignite >> releases. To comply with legal requirements, our community thinks to host >> the fork in a separate Github repo. Are there any alternatives? Is there a >> legal way to host the fork in ASF repos? >> >> [1] https://www.h2database.com/html/main.html >> [2] https://www.h2database.com/html/license.html >> >> - >> Denis >> >
