Timescaledb: Clarification about Timescale License

[tamberg]

released under both the Apache 2 open-source license and the Timescale License

Please clarify both. Is TSL a dual license that can be ignored?

If not, how about moving /tsl to a separate repo?

[mfreed]

Please see our blog post for more information. Once we add more TSL code to that subdirectory, there will be a build flag to bootstrap that will allow you to just -DAPACHE_ONLY=true, so that it will only include the Apache 2 code, and your resulting binary will be purely Apache 2.

Regarding the question about "both":

• The /tsl source code is released under the TSL
• The rest of the source code is released under Apache 2
• The binary one gets from just the Apache 2 source is Apache 2-licensed
• The binary one gets from compiling the TSL and Apache 2 source code is TSL-licensed

For various software and release engineering purposely as outlined in our blog post (similar to what CockroachDB did), we do not want to move these into separate repositories.

https://blog.timescale.com/how-we-are-building-an-open-source-business-a7701516a480

Going forward, our GitHub repo will have both Apache 2 source code and TSL source code (but the latter isolated in a separate subdirectory). An open-source binary only includes Apache 2 code and is covered by the Apache 2 license, while a TSL binary includes both TSL and Apache 2 code and is covered by the Timescale License.