If your organisation uses the open source versions of either Elasticsearch or Kibana in its products or projects, it is now at risk of being forced to release its intellectual property under terms dictated by another.
Well, yeah, it is just more aggressive. But too aggressive for most, if not any use-case.
E.g. do I need to publish the source code of my processor’s microcode? I don’t know, if that in particular is proprietary, but most Linux distros have binary bullshit somewhere down there.
Yeah, so from other info it looks like the scope of the license in much wider than of AGPL and includes other (not well defined) supporting software where in AGPL it only includes the software licensed. Also AGPL kicks in on modification of the software where the SSPL on mere use of it.
So just the fact you install and run some program with SSPL would mean that you suddenly need to licenses who know what else. No other license does that.
Well, yeah, it is just more aggressive. But too aggressive for most, if not any use-case.
E.g. do I need to publish the source code of my processor’s microcode? I don’t know, if that in particular is proprietary, but most Linux distros have binary bullshit somewhere down there.
Yeah, so from other info it looks like the scope of the license in much wider than of AGPL and includes other (not well defined) supporting software where in AGPL it only includes the software licensed. Also AGPL kicks in on modification of the software where the SSPL on mere use of it.
So just the fact you install and run some program with SSPL would mean that you suddenly need to licenses who know what else. No other license does that.