Repository navigation
[License Exception Request] Argo CD vs Redis SSPL #750
Description
Component details
It's Redis as per their annoucement.
License name
SSPL
Code modified?
In Argo CD's case, unmodified from (community) Docker Hub, i just raised this in Argo CD's discussions.
Thusly, Argo CD currently deploys an unaffected 7.0 version of Redis, this issue is about preempting the upcoming change in >=7.4.
Changes contributed?
No response
Any alternatives?
i'm going to leave this question up to more qualified folks
Integrates with other components?
lol yes,
i really don't expect this request to get granted, but we need to start discussing the impact of redis not being OSS anymore asap
Activity
hairmare commentedon Mar 26, 2024
As an alternative to the SSPL (aka MongoDB style) license, Redis is also provided under the (not OSI approved) Redis Source Available License 2.0.
The first "concrete" and public results of the license change I found so far are in gitlab.com/fedora/legal/fedora-license-data#497.
amye commentedon Mar 29, 2024
In the intervening days, a new option has come up: https://github.com/valkey-io/valkey
Would this solve the dependency?
hairmare commentedon Apr 6, 2024
It seems likely that Valkey is going to be the way forward when replacing Redis to solve this dependency.
The Valkey communities work has been very impressive and it looks like we can expect a stable release in due time.
hairmare commentedon Apr 18, 2024
i created a grimoirelab report on cauldron.io to gain further insights. here are some screenshots that visualize the rise of ValKey since the fork. I used the time range 2024-03-22 - 2024-04-18 to generate these.
ValKey
ValKey ranges from a few to several commit per day with issues and review activity to match.
Redis
Redis has infrequent commits and they commit once daily at the most. Their issue created/closed values are similar to ValKey but there is much less review activity.
It's not surprising that Redis has fewer public contributions since the fork, if we look at redis/redis a year ago (2023-03-22 - 2023-04-18), we might get a more reasonable base line comparison
The commit activity from the same time frame in 2023 seems to match current ValKey activity. There was less review and issue activity compared to this year.
Conclusion
I think these early numbers indicate that the ValKey project is off to a healthy start. The comparison to Redis Inc's contribution numbers is interesting, but doesn't provide more value than fancy graphics and should not be used for any decision making. Feel free to rummage through the data set yourself via the link provided above.
I believe it is still too early for our 🔮 to provide proper insights into the future of Redis Inc's source-available offering. But I do think it is safe to say that there is no need for a license exception.
There is a clear direction for the near term that has been confirmed as the way forward in the Argo CD discussion forum and ValKey's BSD-3-Clause license is already on the CNCF Allowlist License Policy.
Given this does not need to go forward, I am closing it as not planned since there is no need to initialize the exception process at this time.
feat(valkey): add managed Valkey service (#3380)