> Technically any license can be changed if the company holds the copyright. If a codebase uses a well-defined license - like, say, the GNU GPL or Mozilla MPL

> Technically any license can be changed if the company holds the copyright. If a codebase uses a well-defined license - like, say, the GNU GPL or Mozilla MPL or Apache license - then unless the company is the FSF, Mozilla, or Apache (respectively), then I know with reasonable certainty that as long as they're using that license with that name, the terms won't be changing under my eyes. The same can't be said of some product-specific "ElasticSearch License" or "CockroachDB License" or "MongoDB License" or what have you. With these, I'm back to having to read EULAs one by one, because the meaning of "$PRODUCT License" can change at pretty much any time. That is, if you're going to jump immediately to some bald-faced snarky ad hominem like > Apparently you could do with a bit of training it would be a lot more effective if you actually understood and acknowledged what I'm talking about instead of going off on some tangent about Microsoft and CLAs.