3 ms·

PSA: their Github repo history still includes the old, un-castrated codebase, and (IANAL), there's nothing in the license forbidding you from still using it. A

PSA: their Github repo history still includes the old, un-castrated codebase, and (IANAL), there's nothing in the license forbidding you from still using it. Adoption of the OSS version must not have been very high, otherwise I would have expected a Valkey / OpenTofu style, community-led fork.

ValentineC 6mo ago
> Adoption of the OSS version must not have been very high, otherwise I would have expected a Valkey / OpenTofu style, community-led fork. I'm guessing battle-tested reliability isn't a priority for calendaring/scheduling web services, unlike Redis/Valkey. It's probably cleaner for anyone looking to adapt the source code to point an LLM at it to extract some specs and tests, then build a new one from scratch.