tejasbaldev

Good luck with suing a ~2 Trillion USD marketcap company. It will drain all your resources to a point of no return.

If anyone is still debating about fairness, philosophical view point, business viability of OSS projects, competition from cloud providers - please click on the link below and check it for yourself.

Link - https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/...

Context : Redis Inc (fka RedisLabs) started creating ''Redis Modules'' later known as Redis Stack to start differentiating with cloud provider's managed Redis. The idea was to keep Redis Core BSD licensed (one of the most liberal licensing model) but at the same time build a layer on top of this BSD layer to keep differentiating the service.

One of these modules was Redis JSON which allowed you to use Redis as a JSON store. One cloud provider copied the whole codebase (even though it was protected by all the licensing clauses) and it doesn't stop there. JSON.FORGET was a cool command created by one of the exes at Redis & the ''cloud provider'' ended up copying that command as well!

If you're still debating whether a company should continue with a liberal licensing like BSD only to allow cloud providers or other service providers to blatantly plagiarise the codebase, think again.

That's exactly the point. Companies providing managed services on top of popular opensource projects are not contributing to the respective OSS project at the scale at which they've been benefitting commercially from these projects.

Could you expand on ''bait & switch''

What exactly is the material impact on a developer with this licensing change? There is a tendency these days to sensationalise things without getting to the bottom of it or even reading the whole article.

What did the OSS Redis project promise a developer that it is not going to deliver in the new licensing model?