2 ms·
> And they did flip those folks a finger and went and made it closed source because they ended up having a spat between businesses. I don't think it's fair to
by tsimionescu 4y ago
> And they did flip those folks a finger and went and made it closed source because they ended up having a spat between businesses.
I don't think it's fair to say ES is now closed source. It's no longer FOSS nor GPL-compatible, but the source is very much still open, and nothing much has changed for many users of the self-hosted versions (source: shipping a proprietary appliance-like product with ES as a component, with full legal checking that we are in compliance of the license).
- josephcsible 4y ago> the source is very much still open You're mixing up open-source with visible-source or source-available.
- tsimionescu 4y agoNot exactly. I explicitly noted that they are no longer FOSS, but I beleive its wrong to call them "closed-source". If parent had said "they are no longer open source", I wouldn't have commented this at all, since "open source" and FOSS are essentially synonyms. But the antonym of FOSS/open source is not "closed source".
- Xylakant 4y agoIt is no longer open source, there’s no doubt about it. You may have a free beer license to it as long as elastic grants you one, but you have no right to modify, patch, redistribute as you see fit. Open source projects that relied on ES are cut off.
- tsimionescu 4y agoYou are still free to modify the code, patch or redistribute it under the terms of the SSPL. If you prefer the ESL, you may only modify the code, but not redistribute it. Now, if you were distributing a GPL product that included ES, you will have significant problems, since the GPL and SSPL are not compatible - so you may in fact be unable to distribute the whole product anymore, which probably caused huge disruptions to some projects - so I'm not in any way saying that what they did is nice. But it was definitely not making it closed source, not in spirit and not in effect.