Live data from Hacker News

ScyllaDB – Why We're Moving to a Source Available License

scylladb.com

31–35 of 35 posts

Re: ScyllaDB – Why We're Moving to a Source Available License

#31
post #28

Earlier quoted context omitted.

Definitely also understand everyone needs to make a living. Buuuttt... projects like these would probably never haven gotten the traction they have now if they wouldn't have started out as opensource but being closed source. For example Hashicorp and Redis definitely wouldn't be where they are today if they had start out as opensource. So in that sense these license changes are a bait and switch.

> For example Hashicorp and Redis definitely wouldn't be where they are today if they had start out as opensource What makes you think there are genuine open source projects that don't get traction? Ansible is still GPLv3 even while owned by RedHat^W IBM and works fine. Any one of the bazillions of front-end toolkits, build tools, bundlers, whatever, many initiated by some company and practically all under open sourc…

I think GP agrees with you. They were saying that Scylladb (or redis, or hashicorp, etc.) never would have gotten as much traction if it had been proprietary from the begining. Being open source helped them get where they are, but now they are abandoning open source.

In fact I strongly suspect that this license change will do more than upset existing users of their open source version, it will scare off potential new users and customers. Not only are they no longer open source, but they gave people a reason not to trust them.

Re: ScyllaDB – Why We're Moving to a Source Available License

#32
post #31
post #28

Earlier quoted context omitted.

> For example Hashicorp and Redis definitely wouldn't be where they are today if they had start out as opensource What makes you think there are genuine open source projects that don't get traction? Ansible is still GPLv3 even while owned by RedHat^W IBM and works fine. Any one of the bazillions of front-end toolkits, build tools, bundlers, whatever, many initiated by some company and practically all under open sourc…

I think GP agrees with you. They were saying that Scylladb (or redis, or hashicorp, etc.) never would have gotten as much traction if it had been proprietary from the begining. Being open source helped them get where they are, but now they are abandoning open source. In fact I strongly suspect that this license change will do more than upset existing users of their open source version, it will scare off potential new…

> I think GP agrees with you. They were saying that Scylladb [...]

Thanks, that was what I was trying to convey. I noticed I made a rather "impactful" mistake in this sentence:

> [...]today if they had start out as opensource[...]

That should read "hadn't"... Sorry about that.

Re: ScyllaDB – Why We're Moving to a Source Available License

#33
post #26

All these mentions of the "ScyllaDB Source Available License" but not even a link towards the actual text. I understand it will have limitations on the data that you can use (up to a certain size) and the CPU power (up to these many cores). Will it also limit the activity type (commercial, SaaS offering, ...)?

They limit only cluster size with 50 cores and 20T disk size. Link to details https://www.scylladb.com/source-available-faq/

Re: ScyllaDB – Why We're Moving to a Source Available License

#35
post #26

All these mentions of the "ScyllaDB Source Available License" but not even a link towards the actual text. I understand it will have limitations on the data that you can use (up to a certain size) and the CPU power (up to these many cores). Will it also limit the activity type (commercial, SaaS offering, ...)?

They limit only cluster size with 50 cores and 20T disk size. Link to details https://www.scylladb.com/source-available-faq/

Thanks!

Although a FAQ is not a real substitute for the actual legal text of the license.

Post reply on HN