4 ms·
I think both are at fault. Amazon for provoking this and Elastic for over-reacting like this and totally break with the open source licensing, when that isn’t n
by VoxPelli 6y ago
I think both are at fault. Amazon for provoking this and Elastic for over-reacting like this and totally break with the open source licensing, when that isn’t necessary to stop Amazon. They could do like MariaDB rather than follow MongoDB: https://perens.com/2017/02/14/bsl-1-1/ https://perens.com/2017/02/14/bsl-1-1/ Would be much more appropriate and alienate the open source community much less.
- StavrosK 6y agoHmm, what's the difference between the BSL and Elastic's license?
- detaro 6y agoCode converts to an open-source license after X (e.g. 4) years in BSL. Time will tell how it works out, especially for mature products it could just mean that everyone targets the 4 year old version.
- VoxPelli 6y agoTime will also tell how eg. SSPL will work if eg. Elastic becomes bankrupt, what happens if I can't get a commercial license for it anymore in 10-20 years? BSL:s expire clause ensures that old code never gets unavailable because the business entity has vanished. Does SSPL have any similar protection?
- dhd415 6y agoNotably, they are apparently considering that: https://www.elastic.co/blog/license-change-clarification https://www.elastic.co/blog/license-change-clarification