2 ms·
> I can read the code, modify it and use in my own projects. That isn't clear. The license language can be read as requiring you to provide the source code for
by tsimionescu 6y ago
> I can read the code, modify it and use in my own projects.
That isn't clear. The license language can be read as requiring you to provide the source code for any software that interacts with ES (e.g., the Linux kernel that you are using to deploy ES over) under the terms of the SSPL to your own users, which you literally can't do.
Elastic claims in their FAQ that this is not the intention, and that may be enough, but it is debatable. Regardless, the SSPL is a bad license for having this ambiguity in the first place.
- dfox 6y agoSimilar kind of ambiguity is even in GPLv2. ie. what does "anything that is normally distributed with..." in section 3 mean and how all that interacts with notionally GPL licensed software which depends on 3rd party components with GPL-incompatible licenses (on Unix-like systems the issue is typically only with OpenSSL but for GPL licensed Windows-only software this is giant can of worms). What makes SSPL and similar freedom-0 ignoring licenses problematic is that you have to care about these kinds of license ambiguities even if you are just using the software.