3 ms·
Nope, code is still available as before and you can make changes and run the code at home/work whatever. It's just if you try to sell ES as a service, then you
by TheChaplain 6y ago
Nope, code is still available as before and you can make changes and run the code at home/work whatever.
It's just if you try to sell ES as a service, then you gotta provide your changes to the public.
- chme 6y ago> It's just if you try to sell ES as a service, then you gotta provide your changes to the public. Doesn't this sound a bit like AGPL?
- karavelov 6y agoYou can run service using AGPL software, you just have to open source your modifications.
- chme 6y agoRight, isn't that what the person I replied to said?
- fabianhjr 6y agoYes, but only for ElasticSearch as a service so having ElasticSearch on your backend won't generally require the distribution of the linked source code.
- chme 6y agoSo there is a distinction between running a ElasticSearch engine with custom changes in your backend and offering a ElasticSearch engine with custom changes to others as a backend? For a non-lawyer that seems very sketchy... I could understand that people would need some legal advice for that, to understand this stuff in detail...
- mindcrime 6y agoNope, code is still available as before and you can make changes and run the code at home/work whatever. That isn't sufficient to be "Open Source". That's more of "Source Available" or "Shared Source" or something.
- throw03172019 6y agoSo if AWS open sourced their version, it would be OK to sell as a service?
- brabel 6y agoAs far as I know AWS's version *is* open source.
- rezonant 6y agoThe new SSPL license requires them to open source a lot more, including user interfaces, backup mechanisms, and anything else necessary to offer the service
- throw03172019 6y agoInteresting. I wonder if this is the reason they published aws-ui to npm yesterday?