If Valkey is the de facto successor of Redis, then maybe abandoning Redict is the right move. If he continued to put effort into Redict, people would just ask why is he wasting time with Redict when Valkey exists.
Note that I generally don’t think time put into free software is wasted, because once its put out into the commons it can be picked up and reused elsewhere - although in this particular case since Redict is licensed under LGPLv3 contributions made to it cannot be reused by Valkey which is licensed under the BSD license. One is, however, free to add their own contribution to both projects as neither requires a CLA, however both do require a Developer Certificate of Origin (DCO) https://codeberg.org/redict/redict/src/branch/main/CONTRIBUTING.mdhttps://github.com/valkey-io/valkey/blob/unstable/CONTRIBUTING.md This is as far as I know an unusual case as generally forks use the same license allowing code to be freely exchanged between them.
As a fork of Redis there is Valkey, maintained by the Linux Foundation and licensed under BSD-3-clause.
If Valkey is the de facto successor of Redis, then maybe abandoning Redict is the right move. If he continued to put effort into Redict, people would just ask why is he wasting time with Redict when Valkey exists.
Note that I generally don’t think time put into free software is wasted, because once its put out into the commons it can be picked up and reused elsewhere - although in this particular case since Redict is licensed under LGPLv3 contributions made to it cannot be reused by Valkey which is licensed under the BSD license. One is, however, free to add their own contribution to both projects as neither requires a CLA, however both do require a Developer Certificate of Origin (DCO) https://codeberg.org/redict/redict/src/branch/main/CONTRIBUTING.md https://github.com/valkey-io/valkey/blob/unstable/CONTRIBUTING.md This is as far as I know an unusual case as generally forks use the same license allowing code to be freely exchanged between them.