The whole redis/redict/valkey forking situation

[Eric Gallager via macports-users]

So one of the stories getting talked about in the FOSS world recently
has been how redis changed its license, leading to some new competing
forks:
https://vickiboykis.com/2024/04/16/redis-is-forked/
This presents a number of questions for what will happen in MacPorts?
- Will MacPorts continue to maintain a redis port?
- Will MacPorts add ports for valkey and/or redict?
- If so, will the 3 conflict, or will they all be installable separately?
- For ports that currently depend on redis, will they continue to
require redis specifically, or will it be possible to use valkey
and/or redict to satisfy their dependencies instead?
- Do any new licenses need to be added to MacPorts' list of recognized
licenses in response to this change? And does
port_binary_distributable.tcl work properly with the new license(s)?
Anyways, this isn't too big of an issue for me personally, as I don't
actually use redis myself, but I figured some other MacPorts users
might appreciate some clarity on the topic...
Eric