Hacker News Reader

So Liquibase made an open-source project, used Apache instead of strong copyleft (e.g GNU AGPL), and then expected others to not do the thing Liquibase chose to allow them: make closed-source derivatives.

Liquibase has only itself to blame.

View on HN

It looks like they auto switch to Apache after some time. I am not sure if that makes it better or worse

Organizations can still achieve their goals with the AGPL instead of a source available license. Redis switched, and their own organization was pleased, as well as their community. I don't think any Liquibase user would be unhappy with Liquibase being dual licensed with AGPL.

AFAIK, AGPL is no-go for EPL/Apache-licensed projects, unless the whole project is under (A)GPL, or use some "exceptions" wording. Wrt Redis community, it's the shadow of the former itself, everyone who plans to invest in Redis long-term, moved to Valkey.

Regarding Redis, you mean that AGPL was not a good choice for them?

It would have been a good choice. They made the wrong choice, lost some community support and then they licensed Redis under AGPL.

Reply on news.ycombinator.com