This article seems to assume that the main problem with this "Commons" rider is a complaint about the "open core" business model. I think that assumption is fa

This article seems to assume that the main problem with this "Commons" rider is a complaint about the "open core" business model. I think that assumption is false. Lots of organizations have "open core" business models, and do not get the rise that this announcement has received. The problem is that this "Commons" rider is confusing and misleading. The term "Commons" makes it sound like this is a Creative Commons license - which it is not. The term "commons" is often used to refer to open source software licenses - which this is not. The coupling with Apache makes it sound like this licensing system is from or endorsed by the Apache Foundation - which it is not. (The article uses the term "Apache Common Clause license" - the fact that author thinks that's a reasonable name, even though Apache didn't create or endorse this license, shows how confusing the situation is.) The Commons FAQ admits that the rider isn't OSS, but then suggests that the OSI definition is some minor technicality - yet the OSI definition is what practically everyone uses, and the "technicality" is at the heart of the point (that everyone can use it for any purpose). Yes, making money is hard. That problem is not limited to OSS either - most new restaurants fail within the first 2 years. I love to see new/better ways to fund OSS. Having a proprietary rider for some modules or having an open core model aren't new ideas, but if they want to do those things (and have the legal right to do), then let's see what happens! But if you're going to create a rider, it's important to actively work to not be confusing. It's hard getting consensus on anything; I think the anger here is choosing names that appear designed to be deceptive. If these names and such aren't changed, I wouldn't be surprised if the Creative Commons Corporation or Apache Foundation start considering a trademark suit to prevent confusion in the marketplace. If they weren't intended to be deceptive - and I hope they weren't - then some renaming and clarification would go a long way.