2 ms·
They don't tend to "kill" the original, they just force them into "source available" licenses. Wikipedia has stuff like MariaDB, MongoDB, Sentry, Redis, etc. as
by camgunz 1y ago
They don't tend to "kill" the original, they just force them into "source available" licenses. Wikipedia has stuff like MariaDB, MongoDB, Sentry, Redis, etc. as some examples.
https://en.wikipedia.org/wiki/Source-available_software https://en.wikipedia.org/wiki/Source-available_software
- Expurple 1y agoIf I understand correctly, Redis-the-permissive-project wasn't threatened by any proprietary fork. What happened is that the financials of its original authors were threatened by AWS hosting Redis as a service. It's not the same as a modified proprietary fork becoming more popular than the original. Redis was relicensed as "source available", and then that license change led to a fork. But the most prominent fork isn't proprietary. It's a permissive one, called Valkey: https://news.ycombinator.com/item?id=44653130 https://news.ycombinator.com/item?id=44653130. That's actually a good example of an in-demand permissive project changing maintainers and staying relevant under a permissive license. An interesting thing to see in the future is whether Redis ("source available" + AGPL) or Valkey (permissive) "wins" in the long term. Too lazy to google the details regarding the other projects.
- camgunz 1y agoAnything hosted on a cloud service is necessarily a proprietary fork: they have to in order to integrate it into their infra. It's not the case they're just loading the docker image and calling it a day.