Maybe this is naive, but some of those bloody license discussions on this thread have hit a nerve.

For my own use in my company or project as an individual

- Can I have full access to the source, clone it and modify it?
YES

- Can I do a pull request to improve it?
YES

- Am I allowed to download, use and have it for free in my company even if my project is commercial and is making money from using Redis?
YES

- Can I create a product that uses Redis as a technology for free in my startup?
YES

- Can I get support if I need it?
YES from github as before or as a paid service from the Redis company

- Is there a lot of people to maintain and do bug fixes?
YES and they are paid a salary to do so

- Is it a me-and-my-cousin project that will be practically abandoned tomorrow?
No. Go check a specific fork's multithreading bugs in github issues. It's scary as fk

- Can I git clone / make / make install it like before?
YES

- Is there new features added or planned to be added?
I guess this is a YES

- Are the people behind the project paid well enough to maintain and support it?
I hope so, certainly it's not best effort after working hours and putting the kids to sleep

- Can I resell Redis as a service taking the source code and running it on my cloud without a paid license?
NO (boo hoo hoo)

Personally I don't care if the definition is open source or SSPL or whatever as long as the project is open code, viable, well maintained and improved. Some complaints here sound like this is a religious thing, and I dislike religious freaks.

I am able to use this software for FREE in my company like I used to. I have access to the source code and I can modify it as I want. I can have my commercial web service that extensively uses Redis as a cache for FREE as long as I don't sell Redis itself as a service to hosting customers. Where's the real problem? Where's the problem with Mongo / Elastic / Redis and the likes who try to fight against abusive tactics of AWS?

If I must add a redis repo and then do apt update and apt install redis... Do I care? Sure, it's an extra step but c'mon. It's 2024, not the 90s. The world has changed. AWS has been "screwing open source projects for more than a decade" (tm)

Why are we scared to face the harsh reality?

Same with Mongo in 2018 and Elastic when they changed their licenses. Same thing, again and again. Nags and complaints from people that, 95% of them, have maybe contributed a typo change in the docs - if so. But they have an opinion about things that are given to them for free and still are free and open. What makes you so entitled? Have you ever said THANK YOU to any of the open source folks? Have you monetarily supported any of them, ever?

Antirez has 21k followers and 9 sponsors who donate on Github. NINE! Not 10, not 50, not 1000 sponsors... it's 9 - a carpenter that lost a finger at work can still count them... You want good open source? Make sure the projects are sustainable, viable and their creators receive love and positive criticism to continue writing code for free for the greater good.

It's only AWS who cares about the license change, no-one else is really affected in reality.

If you're not employed by AWS and you have an issue with Elastic, Mongo, Redis et al changing their license, then you are a convenient fool (sorry). You are not paying good service to the community and the open source movement in it's CORE. OSI execs are happy getting millions from bigcorps in exchange to bending their ethics and views in decision making.

Mongo's discussions with OSI in 2018 is a prime example of that.

AWS is your enemy, not licenses that try to fight against this bully.