13c235484a
Not sure how I missed this yesterday. Signed-off-by: Drew DeVault <sir@cmpwn.com> |
||
---|---|---|
.reuse | ||
deps | ||
LICENSES | ||
src | ||
tests | ||
utils | ||
.gitattributes | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
Makefile | ||
README.md | ||
redict.conf | ||
runtest | ||
runtest-cluster | ||
runtest-moduleapi | ||
runtest-sentinel | ||
SECURITY.md | ||
sentinel.conf | ||
TLS.md |
Redict
Redict is a free software key/value database based on Redis.
What the fork?
This is a fork of Redis 7.2.4 following the announcement that Redis would switch to a non-free license.
This fork is intended to be backwards-compatible with Redis 7.2.4 and then to diverge from then onwards. It should work as a drop-in replacement for Redis 7.2.4, but compatibility with later versions of Redis is not guaranteed. The codebase has been relicensed from BSD-3-Clause to LGPL-3.0-only and will not be using a Contributor License Agreement, which prevents it a similar non-free change from ever taking place in the future of Redict.
More details to come in a later announcement.
Forking in progress...
- Rename binaries
- Update test suite
- Relicense as LGPL-3.0-only
- Update copyright headers
- REUSE for license management
- Rename source files
- Add redict:// protocol support
- Fork Redis modules API
- Rename Lua API symbols (w/compat shim)
- Update test suite to use redict instead of redis
- Update strings
- Update symbols
- Update comments et al
- Update documentation
- Write migration guide
- Create website
- Establish upstream processes
- Contributing instructions
- Code of conduct
- Security issues
- Continuous integration
- Ship a release
Help wanted
Join #redict on Libera Chat and say hello.
Why LGPL?
The Lesser GNU Public License was chosen because it prevents the same thing which happened to Redis from happening to Redict. RedisLabs was only able to produce a non-free version of Redis due to the use of a permissive license; this is not the case with Redict.
AGPL was not chosen because it is not desirable to raise questions about distribution over the network -- unlike RedisLabs we are not especially concerned about having our fork used by cloud providers, we are not attempting to commercialize Redict ourselves. EUPL was rejected for similar reasons.
LGPL was chosen over GPL in order to reduce concerns about issues linking with modules and Lua plugins. MPL was not selected because we'd prefer a somewhat stronger copyleft approach.