Re:Amazon: Not OK – Why we had to change Elastic licensing
by jameshilliard on Tuesday January 19, 2021 @10:11AM
(#25834121)
Yep, it's also incompatible with virtually all copyleft open source licenses. So if you were using any AGPLv3 code with elastic you now have to switch to Amazon's fork.
[ Parent
| on HN ]
Re:Amazon: Not OK – Why we had to change Elastic licensing
by alisonkisk on Tuesday January 19, 2021 @10:17AM
(#25834183)
Is incompatible with non-Affero GPL?
Re:Amazon: Not OK – Why we had to change Elastic licensing
by jameshilliard on Tuesday January 19, 2021 @10:23AM
(#25834264)
Yes, it's incompatible, although you might be fine if you aren't distributing it or running it as a service. SSPL requires re-licensing of all code to the SSPL, GPL has provisions that disallow re-licensing.
> the simple requirement that if you provide the product as a service, you must also publicly release any modifications as well as the source code of your management layers under SSPL
This provision is effectively impossible for anyone to comply with in practice. Calling this a "simple requirement" is a barefaced lie.
Re:Amazon: Not OK – Why we had to change Elastic licensing
by pas on Tuesday January 19, 2021 @10:54AM
(#25834658)
Especially that no independent party with any authority (ie. a court) determined what's covered under "management layers". If I use a custom kernel (that's optimized to run the JVM and has filesystem and block storage optimizations for ES), do I have to provide the source for that? (It seems trivial that it's not "management", but naturally Elastic's interest lies in arguing that yes, that are covered under management layers too.)