Hi Lukas,
> Did you ever think of making JOOQ freely available for Oracle XE? To me >> this sounds like a win win, the open source community could use the >> goodness of JOOQ in the development of oracle targeted projects while JOOQ >> would sell licenses once people have to deploy them to an oracle production >> instance. In other words this would be 1 license per deployer, rather than >> 1 license per developer. >> > > This would be a clear win-lose where "lose" is our part. Having > free-of-charge commercial versions would mean that many prospects would > delay any purchasing decision while using Oracle XE for as long as > possible, or develop against XE and ship to Oracle Enterprise Edition. > I don't think the former would be a common scenario. Who deploys a 1 core oracle instance for production? If that's someones spec then other open source database will likely meet the requirements just as well. The reason Oracle offers this version is exactly because they want people to freely develop against it while making money of the production instances and support. I get the latter problem though which is that companies may let their developers work against XE while then only needing a single JOOQ license for deployments. In open source it may be less of a problem as successful projects have more disparate deployments than contributors. > > We like our developer workstation licenses. You get value out of jOOQ > while developing. Your end users don't get any value out of jOOQ, they will > not be interested in paying for a component of their application. > > I'd love to learn more about your product, plans, community, and perhaps > alternative ideas. > > > http://ecabia.org. The product is just being released under the ASL so there is no community at this point. The thought of requiring commercial licenses for contributors is kind of counter conducive to building one though (especially as academia is a central part of the expected target community). I guess it could somehow be solved by dual licensing and good separation but at this point I'd rather save myself this complication. Apart from that JOOQ fits the requirements of a well designed simplification of internal code that comes without opinionated framework baggage much better than any of the alternatives out there. I can understand though why you came up with the current licensing scheme, it makes a lot of good sense for both parties in many situations. Best of success with JOOQ Timm -- 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.
