Hi Adam, Thank you very much for this very interesting and challenging question. A lot of users and customers ask themselves the same thing. There are two ways to look at this problem.
1. What does it mean, legally 2. Who will continue development Let me answer each question individually: *1. What does it mean, legally* The jOOQ Open Source Edition is not affected by such an "event". It is published under the terms of the ASL 2.0 and will remain available forever from Maven Central. The jOOQ commercial timely unlimited price plans are also not affected by such an "event", because they are... timely unlimited. Besides, all commercial price plans include the right to "modification" along with the delivery of the source code, which means that paying customers can apply any bugfixes themselves as if it were their own code. It was always important to jOOQ for commercial customers not to feel any noticeable difference to the Open Source versions (apart from the fact that the sources may not be distributed). Some of the rationale is also mentioned in this blog post: https://blog.jooq.org/2016/06/30/with-commercial-licensing-invest-in-innovation-not-protection The jOOQ commercial timely limited price plans are also not really affected by such an "event" as the maximum subscription fee increase per year is capped in all existing contracts, although customers might still migrate to a timely unlimited plan at some point. With these legal precautions put in place to protect customer interests, I take that there are no open legal questions / risks. Much more interestingly: *2. Who will continue development* This question is asked often because it is very easy to see what percentage of the contributions would go missing, in the short run: https://github.com/jOOQ/jOOQ/graphs/contributors A lot. But let's answer this question by comparison. A very good comparison would be Hibernate, a competitor product, which is backed by Red Hat. Hibernate is "sold" as a true Open Source community-driven thing. Everyone "owns" Hibernate, or so it seems. But is it true? https://github.com/hibernate/hibernate-orm/graphs/contributors In fact, Steve Ebersole is Hibernate's Lukas. What would happen if this hypothetical "event" happened to Steve Ebersole as it did, fortunately to a much lesser extent, to Gavin King (who was Hibernate's previous Lukas)? The truth is, someone else would pick up developments as both the vendor as well as the community has a lot of interest in it. jOOQ is not a new idea, and it is by far not the only player in the market of Java/SQL internal DSLs (there are also LINQ, QueryDSL, Slick, JINQ, Squill, iciql, and many more). jOOQ is the leading brand in this market, but what is important to understand is the fact that the market responds to real end user needs. Java is everywhere (9M developers use it). SQL is everywhere (almost all developers use it). And the combination of Java and SQL is such a strong force, everyone wants a piece of this market - and thus ultimately - everyone wants jOOQ. Now, rest assured, I do intend to live for another 100 years at least. But regardless of the odds of this happening, with the strength of the market we're in, integrating Java and SQL in the way jOOQ does is what the future wants, and as such, jOOQ will have a brilliant future regardless of who is maintaining jOOQ. Until then, I invite you to enjoy the great value that I'm contributing to the Java/SQL community already today. Lukas 2016-07-21 17:39 GMT+02:00 <[email protected]>: > I'm curious if (god forbid it) something happened to Lukas what the > continuity plan is for jOOQ. > > Who would take the reins? > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
