Redis: "we're doing AGPL again now!"
Proceeds to talk around the issue because they can't bring themselves to admit that they've a mistake, and somehow expects people to trust them again despite showing no evidence that they've learned anything
I'm generally fascinated by this thing where people try to undo a fuckup by just reverting to the old situation and then expect 'business as usual', clearly not understanding that trust is a thing you build up on a social level, and not some deterministic outcome of a set of policies
@gsuberland From what I understand, he left, and then they fucked up the licensing, and now he's back, and it's AGPL again
@joepie91 honestly redis is exactly the same as elasticsearch in my book. It's just not an option anymore.
I guess it's no loss, there are plenty of redis 6+ compatible alternatives and redis 8 has "AI" garbage in it.
@joepie91@social.pixie.town I personally feel like any trust for redis 'org' has diminished. Why would any contributors commit to the project when they can (and maybe will) just pull the rug again? Maybe since it's AGPL this time the fear is less likely, but still.
@joepie91 is antirez still at the helm? if so, this is all the more disappointing - he did a great job with the project in the early days, excellent focus on documentation, helpful responses in issues and with contributors, very responsive on security issues, etc. - but I've heard a few not-so-good things about the redis project governance in recent years.