Re:Openrsync: An implementation of rsync, by the OpenBSD team
by KZerda on Saturday May 30, 2026 @09:55AM
(#48336215)
The BSD license is why we have Valkey and not a purely closed-source Redis. It would have been much easier to perform the rugpull if Redis had initially been GPLed.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by kennywinker on Saturday May 30, 2026 @10:16AM
(#48336462)
On top of badreligion42’s point, that both licenses allow forking just as easily - don’t you have the rugpull part backwards?
Afaik BSD licensed stuff can be re-licensed under any more closed licenses at any time, where as to re-license GPL, you need consent from every single contributor.
But i’m not familiar with the redis-valkey story so, maybe there is some nuance i am missing?
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by KZerda on Saturday May 30, 2026 @10:37AM
(#48336706)
Redis started off as Free Software, but was switched to a source available license in version 7.4. The community promptly forked to Valkey, which is still under the BSD license. Since then, Redis shifted to AGPL 3, with contributor agreements, to try to ensure that they're the only ones who can attempt to commercialize Redis.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by em-bee on Saturday May 30, 2026 @10:47AM
(#48336847)
AGPL makes commercializing harder only for people who fear the AGPL because they want to keep stuff for themselves. there is no problem commercializing it if you don't mind sharing all your connected code. the only benefit redis has is that they can integrate non-free code in their hosting service, while the rest of us could not. since it is their work, i think it is reasonable that they have an advantage. it does not reduce my freedom as a user. it only hinders AWS and other big players from crushing redis.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by badreligion42 on Saturday May 30, 2026 @10:06AM
(#48336347)
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.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by KZerda on Saturday May 30, 2026 @10:24AM
(#48336550)
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.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by akerl_ on Saturday May 30, 2026 @11:01AM
(#48337004)
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.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by WD-42 on Saturday May 30, 2026 @10:53AM
(#48336906)
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.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by em-bee on Saturday May 30, 2026 @10:51AM
(#48336892)
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
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by tardedmeme on Sunday May 31, 2026 @10:54AM
(#48346150)
How would you rugpull a GPL Redis?
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by ranger_danger on Saturday May 30, 2026 @01:26PM
(#48338653)
The paradox clears itself up if you look at what tolerance actually is. It's simply not interfering with people's agency over themselves. Given that your right to self-agency doesn't entitle you to restrict others' self-agency, behavior that does try restricting others' agency is automatically not included in "tolerance."
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by kennywinker on Saturday May 30, 2026 @08:43PM
(#48342032)
Sure, yeah - like most “paradoxes”, it’s not actually a paradox unless you only look at it from one specific viewpoint.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by bigstrat2003 on Saturday May 30, 2026 @06:58PM
(#48341400)
> BSD license is unrestricted, it tolerates taking open source and closing it, thus always being at risk of things closing down.
There is no such risk. If someone wishes to make a closed source derivative of the BSD-licensed original, it does not deprive anyone of the original. That remains there, just as open as before.
Re:Openrsync: An implementation of rsync, by the OpenBSD team
by kennywinker on Saturday May 30, 2026 @08:40PM
(#48342017)
It deprive us of their improvements, while they get to build off other people’s work.
With the GPL, if you want to modify, and built on others work, you have to share.
Share and share alike, vs take if you like share if you like.
BSD license is unrestricted, it tolerates taking open source and closing it, thus always being at risk of things closing down.
GPL license doesn’t tolerate taking from open source and closing it, thus ensuring things stay open.