valkey

> Elastic, Redis, Terraform, now MinIO. Redis is the odd one out here[1]: Garantia Data, later known as Redis Labs, now known as Redis, did not create Redis, nor did it maintain Redis for most of its rise to popularity (2009–2015) nor did it employ Redis’s creator and then-maintainer 'antirez at that time. (He objected; they hired him; some years later he left; then he returned. He is apparently OK with how things ended up.) What the company did do is develop OSS Redis addons, then pull the rug on them while saying that Redis proper would “always remain BSD”[2], then prove that that was a lie too[3]. As well as do various other shady (if legal) stuff with the trademarks[4] and credits[5] too. [1] https://www.gomomento.com/blog/rip-redis-how-garantia-data-p... [2] https://redis.io/blog/redis-license-bsd-will-remain-bsd/ [3] https://lwn.net

I hoped that someone would fork OpenWebUI before the license change an maintain a OSS Version. Like Valkey¹ is the OSS Fork of Redis and OpenSearch² is the OSS Fork of ElasticSearch. [1]: https://github.com/valkey-io/valkey [2]: https://github.com/opensearch-project/OpenSearch

super excited for relaxing the RDB constraints. If you accidentally upgraded beyond Redis 7.2, you likely can just upgrade to valkey without too much effort or any downtime https://github.com/valkey-io/valkey/pull/2543

Looks like the fix was committed three days ago and they cut a release for version 8.1.4. https://github.com/valkey-io/valkey/commit/6dd003e88feace83e... https://github.com/valkey-io/valkey/releases/tag/8.1.4

Well Valkey has more commits to their repository then Redis does, and more contributors. So it appears to be active. https://github.com/valkey-io/valkey https://github.com/redis/redis

Original license of Redis is retained in the form Valkey: https://github.com/valkey-io/valkey/blob/unstable/COPYING Third party licenses retained in a THIRDPARTY file in MariaDB https://github.com/MariaDB/server/blob/main/THIRDPARTY Only two good examples I could quickly find.

> I believe there is a single person that was in Redis and works there now, at least AFAIK. And this person stopped working at Redis long time ago (and was not a core developer). It is probably more correct to say a bunch of Redis contributors left the Redis GitHub project and moved over to Valkey. You can see there are a bunch of contributors listed on this page who seem to predate the fork and who have continued to contribute: https://github.com/valkey-io/valkey/graphs/contributors Particularly these contributors standout: https://github.com/enjoy-binbin https://github.com/madolson https://github.com/soloestoy https://github.com/hwware https://github.com/zuiderkwast https://github.com/hpatro https://github.com/pizhenwei

fork of redis https://github.com/valkey-io/valkey just before the transition to their new source available licenses

The only public record I've seen him talking about it was in https://github.com/valkey-io/valkey/issues/544, where he mentioned having sold the copyright.

We're working on it, you can follow the progress here: https://github.com/valkey-io/valkey/issues/640.

The other is the company that bought the trademark https://github.com/valkey-io/valkey/issues/54.

If you upgraded to 7.4, then redis switched to a proprietary dump format, and if you want to use those dumps you'll have to use a third-party tool to dump the data and put it back in valkey. https://github.com/valkey-io/valkey/issues/845#issuecomment-...

Had a really fun time reading the 8.0rc1 notes a couple weeks back, and diving into the PRs. The PRs on these performance improvements were excellent: very nicely written up PRs, and a logical sequence of work. Of course now there's a great higher level blog post to the topic too. https://github.com/valkey-io/valkey/pull/861 https://valkey.io/blog/unlock-one-million-rps-part2/ There's also a very early RDMA transport, which sounds extremely fun for those so blessed as to be able to try it! https://github.com/valkey-io/valkey/pull/477 I'm impressed with the whole team so much, firing on all cylinders. Great communication in code review, great fast review cycles, smart use of the blog to share updates. Kind of wild seeing smart players from big tech companies collaborating so actively together in public.