Interesting development after almost a year: https://www.theregister.com/2025/05/01/redis_returns_to_open_source/ and https://redis.io/blog/redis-8-ga/ - seems that the new lincence did not help in Redis business at all and Redis 8 returns with "Affero GPL licence". While not as "open" as ASF2.0 or BSD or MIT, this licence is at least OSI compliant. We still would not be able to make it a "mandatory" dependency (it's still fine as optional one according to https://www.apache.org/legal/resolved.html , this is another case (after Grafana and Elastic who did exactly the same) that all kinds of "Business Software Licences" are not good for business long term (which the OSS community was generally quite sure about). Let's see how Affero Licence will work for them.
The interesting thing about Affero licence is that if you build a service and your stack contains "Affero" software - you should either pay, or open-source your entire stack. which is by far most "source-left" licence (and the move is targeted towards all those who get a free software and make money for just making it available as a service). Which I do not like, as this is quite ok to make money - and ASF 2.0 licence is one of the most commercially friendly licence that does not put any limitation on whoever wants to do whatever with the software. BTW. I got (through ASF) with people from the team that helps to move projects to Valkey and they might contribute Valkey support (I told them that we are happy to get a contribution here - but that we aren't actively doing it by maintainers, we will be happy to accept contributions). J On Fri, Apr 12, 2024 at 7:51 AM Amogh Desai <amoghdesai....@gmail.com> wrote: > I too agree with what you are saying, Jarek. > > I do not think there is any direct dependency here from what I know so far. > > Looking forward to when someone adds Valkey support. > > Thanks & Regards, > Amogh Desai > > > On Thu, Apr 11, 2024 at 10:06 PM Vikram Koka <vik...@astronomer.io.invalid > > > wrote: > > > Agree with your assessment Jarek, and that we don't have to do anything > > here. > > > > > > On Thu, Apr 11, 2024 at 5:29 AM Jarek Potiuk <ja...@potiuk.com> wrote: > > > > > Hello here, > > > > > > I've raised the discussion on private@ and it seems that there are no > > > private/controversies there, so I bring the discussion to devlist where > > it > > > belongs. > > > > > > You might want to be aware that Redis announced licensing changes that > > make > > > future Redis 7.4+ releases not good for "mandatory" dependency of > > Airflow. > > > [1]. This is a very similar move to one that MongoDB, Elasticsearch and > > > Terraform did. > > > > > > The RSAL licence is explicitly mentioned in the "Category -X" [2] of > > > 3rd-party licence policy by the ASF as not good as "mandatory" > > dependency - > > > but still allowed as optional [3]. > > > > > > Redis client is MIT licensed and there are no plans to change that - so > > > technically speaking we do not have to limit it in any way. > > > > > > My - personal - assessment is that we are not really affected - even > with > > > our Celery Executor, rabbitmq is still a viable alternative for Redis > > (not > > > mentioning Local and Kubernetes executors), so redis is indeed an > > optional > > > feature. In the future, someone could contribute Apache Qpid [4] > (which > > is > > > supported by Kombu), also an easier one to contribute is to add Valkey > > [5] > > > as an alternative. > > > > > > In the meantime I created https://github.com/apache/airflow/pull/38928 > > to > > > limit Redis image to 7-2-bookworm. > > > > > > Also I'd love personally to see someone to contribute direct Valkey > > support > > > (that would be great I think) - but other than that I think there is > not > > > much we have to do now. > > > > > > But maybe others have different opinions and proposals (and would love > to > > > follow up on it) ? > > > > > > J. > > > > > > > > > [1] > https://redis.io/blog/redis-adopts-dual-source-available-licensing/ > > > [2] https://www.apache.org/legal/resolved.html#category-x > > > [3] https://www.apache.org/legal/resolved.html#optional > > > [4] https://qpid.apache.org > > > [5] > > > > > > > > > https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community > > > > > >
