I think everyone thinks the way they understand open source is the way everyone understands open source. And yet every time an open source project, by any definition, changes their license, people debate what open source really means.
Unlike a term born with a specific definition, like "FOSS", open source doesn't really have a definition. The OSI has a definition that seems to be most popular, but that's not the only understanding of the term that is doing the rounds.
For plenty of people, open source means "source-available software". For others, it's software licensed under a subset of specific licenses (which licenses is also a subject for debate). And for some it means "software developed in a specific way that involves the community", like many Linux adjacent projects are, disqualifying corporate projects licensed under those specific licenses because they can do a Liquibase any time they want and there's very little chance a community large enough to maintain and develop the existing code will stand up when they do.
Liquibase now falls under one of the three definitions I've heard people agree about rather than two.
Funnily enough, the Liquibase project agrees with this sentiment too (or wants to avoid the fallout from open source gatekeepers): https://github.com/liquibase/liquibase/pull/7380
Although, on the other hand, "Two years after release, the license for each applicable version of Liquibase Community code reverts to Apache 2.0". So, it's like... eventually open source. Which is still misleading, as it doesn't apply to the current versions.