3 ms·
I agree in general that reading licenses as a lay person can be problematic. In this case though, TimescaleDB has blog posts that describe the license in very
by GordonS 6y ago
I agree in general that reading licenses as a lay person can be problematic.
In this case though, TimescaleDB has blog posts that describe the license in very plain language, and provide clear examples of what you can and can't do - you can basically do anything except provide it as a service. No need to "wing it".
- mindcrime 6y agoIt's really the general case that I'm interested in. Understanding and dealing with different licenses doesn't necessarily scale well, which is exactly why license proliferation is a Bad Thing. For those people who use Timescale and really like it, and are willing to read and understand this license and then use it, I say "Great!" But in general I find license proliferation to be undesirable and would generally encourage organizations to use standard licenses.
- GordonS 6y agoFair point, I agree with everything you've said here. I do think there is a need for a TSL-like license though, and I think the solution is a new type of widely accepted and understood license, rather than individual companies inventing their own TSL-like licenses. I have no idea how that could actually come to be though.
- fastball 6y agoThe "standard licenses" you're talking about weren't standard until people actually started using them. People can't start using licenses if you don't first write them.
- mindcrime 6y agoThat's fair. And if there's a market for this kind of license, then it will catch on. And if it does, then so be it. I doubt it's a license I'd use, but I don't begrudge these guys any success they have.