So I guess the options are now to use the “OpenDistro” [0] or the SSPL distro maintained by Elastic.
It’s too bad that Elastic is no longer open source, but respect the companies choice to close source their stuff.
Will be interesting if Amazon just maintains their fork or abandons it to make something else.
I’m not familiar with elastic as a project and not sure how many community contributions they have, but expect that to shrink as I’m not sure many OSS developers will freely contribute to non-OSS projects.
As for trademark stuff, I expect a renaming like Hudson/Jenkins.
I think you are grossly over estimating the contributions that the general community has to open source. Theres a company behind this project and they do most of the maintenance work.
Yep, this happens with alot of open source. Either a big company maintains a project through paid engineers. OR some poor guy gets burnt out because everyone is demanding free changes to some OSS package constantly without providing PR/MRs.
Exactly, which is why I hope Elastic manages to beat Amazon wih this tactic since it then can be a playbook for OSS companies. In general OSS is fantastic whether free or paid and I genuinely want companies like Elastic to succeed. This whole free software thing is stupid and it is sad to see talented devs getting burnt out because people are cheap to pay for software.
I make products that use that package. I want all the packages I depend on to be compatible with my license. I don’t want to run into an audit years from now during due diligence that I have some liability from an incompatible license.
I can’t afford lawyers to determine compatibility today. And I suspect that they would say “not compatible, pay to be safe.”
This sounds more like an issue with the licensing world itself than with this license, which by itself is pretty simple and won't affect you except in the case you offer your products containing Elastic as a service to third parties.
It’s too bad that Elastic is no longer open source, but respect the companies choice to close source their stuff.
Will be interesting if Amazon just maintains their fork or abandons it to make something else.
I’m not familiar with elastic as a project and not sure how many community contributions they have, but expect that to shrink as I’m not sure many OSS developers will freely contribute to non-OSS projects.
As for trademark stuff, I expect a renaming like Hudson/Jenkins.
[0] https://github.com/opendistro-for-elasticsearch