Redis should step up and fund an independent foundation now and encourage Valkey...

_msw_ · 2025-05-01T17:15:35 1746119735

Why? They can already just copy the code they want from Valkey, since Valkey is 3 clause BSD...

But maybe Valkey should switch to GPLv3 instead to correct this imbalance.

https://github.com/redis/redis/pull/13638

gray_-_wolf · 2025-05-01T17:45:08 1746121508

I am not sure what that would achieve? Combining programs under GPLv3 and AGPLv3 is possible (the resulting work is under AGPLv3).

jraph · 2025-05-01T18:14:35 1746123275

The imbalance I think _msw_ refers to is the fact that Valkey couldn't both take code from a GPL-licenced Redis and keep its license.

So either they relicense, or they can't take code from Redis but Redis can take code from Valkey.

gray_-_wolf · 2025-05-01T18:22:37 1746123757

I see, I misunderstood that. I have read it as an attempt to prevent redis taking the code from valkey.

However, if the intention was the other way (to allow valkey to take code from redis), valkey should just go for AGPL as well, there is little reason to pick GPL if the code sharing would be the motivation for the license change.

_msw_ · 2025-05-01T18:23:45 1746123825

Disclaimer: I am not a lawyer, this is not legal advice.

In theory, one would not be able to offer a combined program under other licenses (in particular, RSALv2 and SSPLv1), as those licenses have conflicts with GPL obligations.

Direct contributions to the Redis project avoid this issue via a separate Contributor License Agreement. It would only mean that Redis developers could not unilaterally copy code from Valkey.

I'm not saying that the Valkey community should do this. Personally, I think it's better off as a BSD-3 licensed project, with the community fulfilling the promise made by others that it would always be that way.