I'm not sure sure it will go "badly". I believe there's a fundamental issue with a class of software applications that the current OSI licenses don't do much fo

I'm not sure sure it will go "badly". I believe there's a fundamental issue with a class of software applications that the current OSI licenses don't do much for. Let me clarify that statement with some examples. If you're a developer of an "open source" library or database engine, you have great OSI licenses available to use. The consumers of your work will either open source their work or purchase a license (i.e. dual-licensing). If, however, you're creating a CMS or some standalone tool (like GIMP, for example), you're left to go down the road of open core (typically). So, the alternative here is to choose a license that's conducive of being able to monetize without depending on donations or support contracts. I think developers should pick a license that makes sense for them, not necessarily for the benefit of others. What is important though, is that some thought is taken and to try it out. You can always go more permissive later. I'm working on something that I want to monetize, but the OSI licenses aren't helpful for the kind of application I'm working on. I'm leaning towards a similar licensing structure and have been spending a great deal of time thinking about this and I hope to have more discussions on this very topic as it's extremely helpful for everyone. edit: typos