> My thought is not to restrict anyone from doing anything. Rather that, for example, any profit-seeking entity can use any code, but that that profit-seeking entity must pay a standard and proportional fee to the license-holder of that code, generally its author(s) and/or maintainer(s).
Well, so you are effectively restricting the field of endeavor. People who want to do business with the code licensed this way can no longer do so without having to pay while all others still can use the code freely. I don't think there's much room for interpretation as to whether this fulfills the term "discrimination".
What you can do instead is dual-license your code, offering more "favorable" terms in a second proprietary/commercial license to businesses. However, this usually comes with the caveat that licensees of the commercial license can now do proprietary changes without having to give them back to the community.
> the GNU/GPL don't qualify as "open source" software.
> It is to laugh.
What? I am afraid you are misinterpreting the text and/or confusing the terms of the General Public License. This says you should not place restrictions on the licenses of other software contained on the same medium. It doesn't say anything about derivative work. Why would this mean the GPL doesn't qualify as an open source license?
My observation is fundamentally that if open source can be cannibalized by profit-seeking entities, it will be so cannibalized.
It’s true that I haven’t comprehensively studied the GPL.
Mostly I’ve observed companies using hundreds, thousands, or millions of hours (depending) of the very hard work of many very smart open source devs in building their own proprietary systems on top and making fucktons of money, none of which is ever seen by the people who made 90 or 95% of their business possible.
Well, so you are effectively restricting the field of endeavor. People who want to do business with the code licensed this way can no longer do so without having to pay while all others still can use the code freely. I don't think there's much room for interpretation as to whether this fulfills the term "discrimination".
What you can do instead is dual-license your code, offering more "favorable" terms in a second proprietary/commercial license to businesses. However, this usually comes with the caveat that licensees of the commercial license can now do proprietary changes without having to give them back to the community.
> the GNU/GPL don't qualify as "open source" software.
> It is to laugh.
What? I am afraid you are misinterpreting the text and/or confusing the terms of the General Public License. This says you should not place restrictions on the licenses of other software contained on the same medium. It doesn't say anything about derivative work. Why would this mean the GPL doesn't qualify as an open source license?
Here's a list of all OSI approved licenses: https://opensource.org/licenses/alphabetical