Is #redispy going to support #Valkey? I would guess not?
#Redis Inc appears to be in complete control of the library, I don't see why they'd support forks they're hostile to:
#aioredis got merged into redis-py and is now archived
♡ 0 ↻ 0
#Redis
#AWS #Redis #Elasticache For all your elastic-ache needs, AWS is participating in #Valkey the SAAS-safe fork of Redis
https://www.linuxfoundation.org/press/linux-foundation-launches-open-source-valkey-community
Can a fork (i.e. not original copyright holder) relicense from from BSD-3-Clause to LGPL-3.0?
Barrister Google seems to think you are very limited in what sort of relicensing you can do (i.e. you can only adopt *more* restrictive licenses, otherwise why not fork everything and change the license to public domain?)
Anyhow care to speculate if #AWS will fork #redis the same way they did with #elasticsearch ? My guess is it depends on how much business they're doing with #elasticache