[badreligion42]

And how exactly did the BSD license make creating Valkey easier? GPL and BSD licenses both have the source in the open. Anyone creating a fork, can easily do so for either BSD or GPL licensed projects. Since Redis is a database, which the user won't be using a binary of, even using a fork of a supposedly GPL-licensed Redis would not require you to share your modifications with your user, same as BSD.

[KZerda]

The BSD license made forking Valkey easier because it ensures that everyone has equal footing. The GPL, especially with contributor license agreements and the like, makes it much more easy for a single party to control the direction of the product. For another example of this happening, look at MongoDB. It started out under the AGPL, but was rugpulled to a non-free license.

[akerl_]

It feels like your actual beef here is with CLAs, which often are designed to allow the current maintainers to relicense.

CLAs are not an attribute of the GPL. They're an agreement that can be applied to contributions to any codebase with any license.

[em-bee]

The BSD license made forking Valkey easier because it ensures that everyone has equal footing

equal footing on the license is what allowed AWS to crush the original creators of the products they host.

it's a trade off.

the AGPL does not prevent a hosting service. it only prevents creating non-free addons. i see no problem with that. see also my other comment

[WD-42]

Mongo was already a centralized project. Technically open source agpl but I don’t remember it having a large developer community or really many contributions from outside mongo. When the rug pull happened I think simply most people didn’t care or moved on to equal (or better) alternatives. It’s not beloved software like Redis is.