affects 1067413 + redis-server
thanks
Hi Guillem,
> I'm CCing Chris, who might perhaps be interested in replacing Redis with
> KeyDB as its spiritual successor and taking this on? Or if not, at least
> to perhaps potentially coordinate some kind of transition, even though
> we've had issues migrating persistent DBs from newer Redis to KeyDB, so
> that might be tricky or not feasible at all.
Thanks for including me here. I had not yet looked into potential
Redis replacements nor the exact and precise details of the new
license etc. and this activity around KeyDB feels like a good start.
I thought I'd let the dust settle for a bit before making any
decisions — perhaps the change even gets reversed (!), and no doubt
there might be new alternatives that will fork the code immediately
prior to the license change.
My personal and professional usage of Redis has dropped off in the
past few years, so it would make more sense for me to help out in a
team maintainership role, at least with respect to KeyDB.
However, I'd be interested in coordinating around some kind of
Redis→KeyDB/something transition if need be.
(Incidentally, why did your work switch to KeyDB?)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
