Hacker News Reader

Comment by eatonphil | Hacker News Reader

Well they didn't do it backwards compared to at least some subset of peers.

  Cockroach: Apache -> BSL https://www.cockroachlabs.com/blog/oss-relicensing-cockroachdb/

  Mongo: AGPLv3 -> SSPL https://techcrunch.com/2018/10/16/mongodb-switches-up-its-open-source-license/

  Elasticsearch: Apache -> SSPL https://www.elastic.co/blog/licensing-change

I am sure there are more I'm forgetting.

Edit: Removed MariaDB.

View on HN

MariaDB is still GPL. That article references some kind of scaling add on, not the core product.

Ah, you're right.

Yeah I was about to raise the pitchforks, I hadn't heard of MariaDB abandoning open source!

this is a great point...further down the comments, an OpenTF maintainer made a great point that all of these services are "backend hostable" services. Terraform doesn't even have a backend service component...Terraform Cloud does, but not Terraform itself.

I didn't contemplate this when writing the article but it seems like this might be a pretty big factor in the reaction to the change. At least to my memory, I don't remember as strong as a pushback from any of these companies changing their licenses

> I don't remember as strong as a pushback from any of these companies changing their licenses

The Elasticsearch backlash was big for what it's worth, both privately inside companies and publicly (AWS forked it).

ah wow...I guess that begs the question, "will this just blow over". As far as I can tell Elasticsearch continues to do well and is more or less in the clear (could be wrong)

Redis Labs, Confluent. Pretty sure I'm forgetting some of the smaller Commons Clause adopters.

Literally every one of these examples is a database and terraform is a dev tool

Reply on news.ycombinator.com