Hi Lukas, I agree with you an Lewis. I also think that options 1 and 2 would be the options to follow if we decide to work with jOOQ. I don't remember where I read that all code that comes from Apache Projects has to be ASL and that would be option 1 right? We might need to confirm this with someone more experienced in licensing. Besides this I think we should take a vote on using jOOQ for rewriting the SQL module and put it on our roadmap. I don't think there is anyone that will vote against it, but maybe someone has a compelling reason to rethink this. Maybe we can think about this at some point of 0.4?
Renato M. 2013/11/18 Lukas Eder <[email protected]> > Hi Lewis, > > No worries at all for the delays! I understand. Good things come to those > who wait, right :-) > And thanks for adding that other list. I must've been confusing some > mailing lists. > > So, while Option 1 is the option that you can use any time, Option 2 will > give you more long-term stability. > I think that regardless of your development progress, I can already > prepare a tailor-made license agreement between Data Geekery and the Apache > Gora project, which includes: > > - Apache Gora may use jOOQ Enterprise Edition on an unlimited amount > of developer workstations for free for integration tests > - Apache Gora is required to place a prominent backlink to the jOOQ > website, indicating that Apache Gora is built on top of jOOQ > > Do you agree with proceeding this way, or would you prefer to wait? > If you agree, whom will I direct this agreement to, for review? > > Cheers > Lukas > > From: Lewis John Mcgibbney [mailto:[email protected]] > Sent: Montag, 18. November 2013 15:33 > To: Lukas Eder > Cc: [email protected]; <[email protected]> > Subject: Re: Apache Gora and jOOQ > > Hey Lukas, > N.B. Including dev@gora list here to keep everyone in the loop. > > Thanks for keeping this thread alive. I personally would like to apologize > for not dropping in on this one earlier. My resources have been focused > elsewhere as of late and I have not had the JOOQ initiative at the top of > my TODO list. > Regarding your points/options please see below > > On Fri, Nov 1, 2013 at 7:42 PM, Lukas Eder <[email protected] > <mailto:[email protected]>> wrote: > 1. Apache Gora links and embeds only the jOOQ Open Source Edition, which > is available and will continue to be available from Maven Central under the > terms of the ASL 2.0. For Apache Gora, there are no additional license > terms. For your end users, there aren't any additional terms either, if > they're using Apache Gora with an Open Source database. If end users wish > to use Apache Gora with SQL Server, for instance, they would need to > purchase a license from Data Geekery and replace jOOQ Open Source Edition > binaries with jOOQ Professional Edition binaries. In this case, Data > Geekery would welcome but not require a backlink indicating that Apache > Gora is based on jOOQ. > > This sounds like the most realistic option IMHO. At the end of the day we > (Gora) as an Apache top level project are in no position to change the > terms and/or add to the Apache License v2.0 in any way. What is slightly > annoying right now is that a good re-write of the gora-sql module to > implement JOOQ is extremely attractive for us at Gora but it appears the > development cycles are not there right now! > > > 2. In addition to the above, Data Geekery and Apache Gora could make a > separate agreement, which grants Apache Gora a perpetual license to use the > jOOQ Enterprise Edition for integration testing Apache Gora against SQL > Server and other commercial databases, but not to distribute, sublicense or > make available the jOOQ Enterprise Edition to end users. End users may > again use Apache Gora with the jOOQ Open Source Edition along with Open > Source databases, or they may purchase a commercial license from Data > Geekery. In this case, Data Geekery would require a prominent backlink > indicating that Apache Gora is based on jOOQ. This is how IntelliJ or > YourKit Profiler handle free commercial licenses for non-commercial OSS > projects as well. > > This is also very attractive as it would enable us to verify gora > compliance with commercial RDBMS... always a bonus to promote Gora to more > people. > > > 3. Data Geekery and Apache Gora will make a separate agreement, which > grants Apache Gora a perpetual license to use and distribute the jOOQ > Enterprise Edition, but not to sublicense jOOQ or to make the jOOQ API or > binaries available to end users (e.g. by embedding the jOOQ jar file). Of > course, there are technical ways to circumvent this restriction and > "extract" jOOQ from Apache Gora. Hence, there would need to be additional > terms to YOUR license, clearly indicating that only Apache Gora code is ASL > 2.0 licensed, whereas jOOQ binaries are jOOQ-licensed. I suspect that this > would make Apache Gora dual-licensed, as well...? This case would be based > on a discounted license paid by Apache Gora backers. Your end users would > not need to license jOOQ. > > Personally, I feel that 1) or 2) is the easiest for you guys to handle. > > I agree with you here Lukas... I think that the first two options are most > likely at this stage. We would pull in the ASL v2.0 licensed JOOQ maven > artifacts as part of our gora-sql pom.xml, use the open source code and > leave it down to module users if they wish to pursue a separate agreement > with DataGeekery. > > > Let me know what you think, > Lukas > From my point of view this is something which sounds like a positive thing > to progress with but as I said above my time and commitments are elsewhere > right now. I am not in a position to begin writing the SQL module back in > to Gora right now :( > >
