Yes, nobody says that there's something illegal here. Were it so, Redis is high enough profile project for someone to take a legal action.
But this is a takeover that is slowly draining the value from the community and directing it to private pockets. E.g. Redis is now source-available.
There are still compatible alternatives: https://valkey.io/ (C, a direct Redis fork) or https://keydb.dev/ (C++, an evolved Redis fork), both BSD-licensed.
I wish RethinkDB was more alive :-\
> But this is a takeover that is slowly draining the value from the community and directing it to private pockets. E.g. Redis is now source-available.
I think you're fooling yourself into believing that Redis was ever a community-owned project.
The truth of the matter is that the guy who developed Redis ended up selling Redis to a corporation. Since then he bailed out, and the corporation that owns Redis is now going through great lengths to monetize it.
The faster you forget about Redis and switch to alternatives, the better you'd be.
My point is the lesson here should be to wary of tools that don't have a foundation backing them. I have nothing but the highest respect for antirez. But redis never had a foundation. That makes it susceptible to be source-available. The same with Elastic search.
I think the best option against this action by Redis Inc is to move to valkey and use it to incorporate features that Redis Inc considers "enterprise licensed features". If there are big players in valkey, there should be a move to setup a foundation for it - so that it doesn't get taken in to be source available again.
> But redis never had a foundation.
In theory Redis could have had a foundation. It didn't. Instead the project owner opted to sell it to a corporation. This doesn't happen by accident.
What indeed has a foundation is Valkey[1]. It's backed by the likes of AWS, Google Cloud, Digital Ocean, etc.
[1] https://www.linuxfoundation.org/press/linux-foundation-launc...