Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem?
Locked
 
|
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 |
|
|
Adding a valid legal mailing list.
- Denis On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 > |
|
|
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 <[hidden email]> wrote: > Adding a valid legal mailing list. > > - > Denis > > > On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 >> > |
|
|
Hen,
Ignite community knows that the changes will be available under non-Apache 2.0 license and doesn't see this as a showstopper for contribution. Some community members will be contributing to the H2 fork owned by the community. The question is where can we host this fork. If the fork can be located in ASF-repositories then we'll keep it on Github. Thanks, Denis > From: Hen <[hidden email]> > Date: Tue, Jul 9, 2019 at 1:02 PM > Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? > To: <[hidden email]> > Cc: dev <[hidden email]> > > > 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 <[hidden email]> wrote: > >> Adding a valid legal mailing list. >> >> - >> Denis >> >> >> On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 >>> >> > > -- > Удачи, > Денис Магда > |
|
|
Denis
Stepping backwards from the legal question: why does the Ignite community feel that they need to fork H2? Can the community simply not work to contribute your desired changes to the upstream H2 community? Rob From: Denis Magda <[hidden email]> Reply-To: <[hidden email]> Date: Wednesday, 10 July 2019 at 00:43 To: <[hidden email]>, <[hidden email]>, dev <[hidden email]> Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? Hen, Ignite community knows that the changes will be available under non-Apache 2.0 license and doesn't see this as a showstopper for contribution. Some community members will be contributing to the H2 fork owned by the community. The question is where can we host this fork. If the fork can be located in ASF-repositories then we'll keep it on Github. Thanks, Denis From: Hen <[hidden email]> Date: Tue, Jul 9, 2019 at 1:02 PM Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? To: <[hidden email]> Cc: dev <[hidden email]> 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 <[hidden email]> wrote: Adding a valid legal mailing list. - Denis On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 -- Удачи, Денис Магда |
|
|
Rob,
That's the right question. Basically, future plans of H2 community doesn't align with Ignite needs. We made several contributions to the upstream, but the next changes are not of H2 roadmap interest. Ignite community will be adopting H2 fork for the distributed SQL engine needs (special memory management and execution planner related optimizations). Ok, thanks to everyone responded. I think that the only way is to make that fork in a separate Github repo and produce binaries for Ignite needs. This solution doesn't have any license-related issues. - Denis On Wed, Jul 10, 2019 at 1:28 AM Rob Vesse <[hidden email]> wrote: > Denis > > > > Stepping backwards from the legal question: why does the Ignite community > feel that they need to fork H2? > > > > Can the community simply not work to contribute your desired changes to > the upstream H2 community? > > > > Rob > > > > From: Denis Magda <[hidden email]> > Reply-To: <[hidden email]> > Date: Wednesday, 10 July 2019 at 00:43 > To: <[hidden email]>, <[hidden email]>, dev < > [hidden email]> > Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? > > > > Hen, > > > > Ignite community knows that the changes will be available under non-Apache > 2.0 license and doesn't see this as a showstopper for contribution. Some > community members will be contributing to the H2 fork owned by the > community. The question is where can we host this fork. If the fork can be > located in ASF-repositories then we'll keep it on Github. > > > > Thanks, > > Denis > > > > From: Hen <[hidden email]> > Date: Tue, Jul 9, 2019 at 1:02 PM > Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? > To: <[hidden email]> > Cc: dev <[hidden email]> > > > > 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 <[hidden email]> wrote: > > Adding a valid legal mailing list. > > > - > > Denis > > > > > > On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 > > > > > -- > > Удачи, > Денис Магда > > |
|
|
Agreed that that seems the most likely course.
A random set of individuals who may or may not overlap with the individuals who are a part of Apache Ignite launch a new project on GitHub and Apache Ignite depend on it akin to their dependency on H2. Which seems like a decision made by inertia - we will only publish Apache 2.0 licensed projects because <for reasons; most of which equal we have a license of our own>. While I think you should go ahead and do the above, I also think the ASF should be asking itself whether there is any real reason why it couldn't host that H2 fork. Hen On Wed, Jul 10, 2019 at 1:01 PM Denis Magda <[hidden email]> wrote: > Rob, > > That's the right question. Basically, future plans of H2 community doesn't > align with Ignite needs. We made several contributions to the upstream, > but the next changes are not of H2 roadmap interest. Ignite community will > be adopting H2 fork for the distributed SQL engine needs (special memory > management and execution planner related optimizations). > > Ok, thanks to everyone responded. I think that the only way is to make > that fork in a separate Github repo and produce binaries for Ignite needs. > This solution doesn't have any license-related issues. > > - > Denis > > > On Wed, Jul 10, 2019 at 1:28 AM Rob Vesse <[hidden email]> wrote: > >> Denis >> >> >> >> Stepping backwards from the legal question: why does the Ignite community >> feel that they need to fork H2? >> >> >> >> Can the community simply not work to contribute your desired changes to >> the upstream H2 community? >> >> >> >> Rob >> >> >> >> From: Denis Magda <[hidden email]> >> Reply-To: <[hidden email]> >> Date: Wednesday, 10 July 2019 at 00:43 >> To: <[hidden email]>, <[hidden email]>, dev < >> [hidden email]> >> Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? >> >> >> >> Hen, >> >> >> >> Ignite community knows that the changes will be available under >> non-Apache 2.0 license and doesn't see this as a showstopper for >> contribution. Some community members will be contributing to the H2 fork >> owned by the community. The question is where can we host this fork. If the >> fork can be located in ASF-repositories then we'll keep it on Github. >> >> >> >> Thanks, >> >> Denis >> >> >> >> From: Hen <[hidden email]> >> Date: Tue, Jul 9, 2019 at 1:02 PM >> Subject: Re: Place for MPL 2.0/EPL 1.0 source code in ASF ecosystem? >> To: <[hidden email]> >> Cc: dev <[hidden email]> >> >> >> >> 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 <[hidden email]> wrote: >> >> Adding a valid legal mailing list. >> >> >> - >> >> Denis >> >> >> >> >> >> On Tue, Jul 9, 2019 at 12:46 PM Denis Magda <[hidden email]> 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 >> >> >> >> >> -- >> >> Удачи, >> Денис Магда >> >> |
«
Return to Apache Ignite Developers - Legacy Mail Archive
|
1 view|%1 views
| Free forum by Nabble | Edit this page |