4 ms·
> Really the only practical limitation that I can see now is if you're AWS you can't launch a competing service with Timescale by leeching off their software wi
by yjftsjthsd-h 6y ago
> Really the only practical limitation that I can see now is if you're AWS you can't launch a competing service with Timescale by leeching off their software without paying for it. That's a glaring short-coming of FOSS licenses that really should be addressed
Then use AGPL?
- xyzzy_plugh 6y agoHow does AGPL address this?
- yjftsjthsd-h 6y agoThe original problem was Amazon "leeching off their software without paying for it". If Amazon shares their changes (as the AGPL requires), then they're contributing, not leeching. If the problem is just that Amazon happens to use a product, or horror of horrors, offer a hosted version... I dunno, I just can't see what the issue is. Is every developer upset about people profiting off their work sending a monthly check to Linus Torvalds for using Linux, Apple for clang and/or GNU for gcc, and the maintainers of their distro of choice? Or is only their software that nobody else is allowed to make money off of?
- ivalm 6y agoTimescaledb the company wants to make money from their managed service, thus they are protecting it from competition. That’s fine. They are not true open source but that’s fine too.
- yjftsjthsd-h 6y agoAgreed. I don't mind companies selling proprietary software. I do mind companies trying to claim that they're offering open source software when they're actually offering source-available software. With the Apache2 version, Timescale actually appears to be doing both, but I can't find a description of the differences so I can't comment very well; I assume they're doing open core. Which, again, is fine as long as you don't try and pretend that you're doing something else.
- mfreed 6y agoYes, our offering is of the "open core" nature, although our non-open-source code is covered under the Timescale License (source available, free). For most "open core" companies, this latter part is instead closed-source and paid, hence this terminology also leads to confusion :) Anyway, here's the link to license pointers in github, and you can find all code there: https://github.com/timescale/timescaledb/blob/master/LICENSE https://github.com/timescale/timescaledb/blob/master/LICENSE Source code in this repository is variously licensed under the Apache License Version 2.0, an Apache compatible license, or the Timescale License. All source code should have information at the beginning of its respective file which specifies its licensing information. * Outside of the "tsl" directory, source code in a given file is licensed under the Apache License Version 2.0, unless otherwise noted (e.g., an Apache-compatible license). * Within the "tsl" folder, source code in a given file is licensed under the Timescale License, unless otherwise noted. When built, separate shared object files are generated for the Apache-licensed source code and the Timescale-licensed source code. The shared object binaries that contain `-tsl` in their name are licensed under the Timescale License.
- majormajor 6y agoIf Linus had wanted users to pay him I certainly wouldn't pay a different company for it, if they just copied his code and didn't forward of the money on... I do wonder, in a non-free world like that, if we'd have a higher proportion of "tech giants" still in the "making software" space instead of being so advertising-centric with Google, Facebook, etc's, main revenue streams.
- mfreed 6y agoThe AGPL allows Amazon to offer a competing service. It just needs to be open-source. But the cloud vendor's efforts aren't typically with the software itself -- they often run the open-source version unmodified -- but rather with the operations and systems around the software. Mongo's SSPL was trying to block this case by forcing folks to open-source all their surrounding infra (which likely AWS would never do), but at least for now, the SSPL was not accepted as an Open-Source License by the OSI. Also, I'd argue that efforts like the SSPL are actually trying to "backdoor" the goal of "cloud protection licenses" in the first place. They are trying to bake-in a poison pill that the cloud vendors won't want to do, as opposed to having a clause that just directly speaks to the stated goal.
- JoshTriplett 6y agoThe SSPL has at least some hope of potentially being a viable FOSS license; the disagreements around that license were around details and implementation, not necessarily critical unfixable issues. Something like the Timescale license fundamentally can never be a FOSS license.
- _msw_ 6y agoI don't agree, Josh. Certainly not v1 (which, AFAIK, is the only version in use). I doubt v2 could gain broad support either.
- JoshTriplett 6y agoI'm not suggesting it could trivially become an OSI-approved license. Rather, I think it's much closer in spirit than something like the Timescale or "Commons Clause" or similar licenses, that blatantly discriminate against fields of endeavor (OSD 6) by design. The SSPL, by contrast, is a copyleft license that has a much stronger copyleft than the AGPL. It may potentially be overstepping the intent of what the OSD means to allow, but it doesn't on its face violate the spirit of any of those clauses, not any more so than the AGPL does. I think it'd be possible to modify the SSPL into a version that could meet that agreement while maintaining the intent of the license.