[sonarlunar]

It's one vendor contributing some modules which now they have a different license.

I don't see how this impacts any other Redis module on github out there.

Either those modules are that good and the vendor decides that cloud providers must pay and not get money from the vendor's work, or those modules are not really that used so who cares.

I have used RedisJSON module which is nice and I assume changes license now. Am I a service provider? Do I care about one module changing license so AWS and other clouds cannot use for their own service?

I couldn't care less and it does not impact Redis open source project at all IMHO

[hashrate]

> I couldn't care less

Let's say you are PHP consultant , you set up a Redis + EC2 instances.

You enable a redis enterprise module in that instance.

Well technically speaking you are breaching the license of RedisLabs. You are not allowed to do so without their consent because those modules aren't "bsd" or "mit" they are "Commons Clause".

In short , if you are doing something with the RedisLabs modules ( consulting / hosting / training / support ) you owe $$$ to RedisLabs.

[sonarlunar]

It's unenforceable. European Union cannot claim VAT from smaller - yet big enough - foreign companies and is only targeting the very big ones to collect it from. I used to play an online game and, if you changed your country to a non EU one, no VAT was paid. And that was a big company that should have been enforcing EU VAT for me.

Would Redis Labs go after Joe and his brother? Even if the license said so? They're after the big abusers, not the community.

If I'm not mistaken antirez said so too, that it does not affect you and me. That's the reasonable thing anyway. AWS is the big abuser. Check MongoDB or Xen or Elastic cases. People (ex employees typically) are starting to talk how AWS is abusing their open source work. I think that's the whole juice of the story, that AWS is abusing successful open source projects.

At least that's what I read behind the words.