Too much spaghetti too much legal jargon it turns anybody off NOT to read ! Before voting, could you please provide some real world EXAMPLES, not just jargon.....
Examples how it would apply to each vote.......Such as I create a game using ENIGMA, I do this, I do that, this is allowed, this is not, using an example and not just repeating words from the license, so most of us license illiterates can better understand, because I'm pretty sure most people have at one time violated one or more licenses unintentionally, because of the long winded legal jargon that makes you dizzy !
So here is a template:
I use ENIGMA to create my game.
Along with ENIGMA I use other 3rd party open source OR I use my own proprietary code that I embed inside the ENIGMA OR that I call externally......
Or how about this, so long as ENIGMA was not modified and integral and used to making your games, your game would not require source availability. In other words you can license your creation as you want (without having to distribute its source) BUT mentioning ENIGMA used or not or whatever, which license would be best for that....
I recall these long debates light years ago with never-ending debates on down sides of each.
So it's always a damned if you do damned if you don't scenario.
Perhaps if there were more concrete examples of how this could apply instead of citing back the jargon, it would help the masses.
A lot of people violate licenses, every second, thousands of people do......How many get caught is the question......too few......how many worthwhile being perused, again good question.......point being most people don't read licenses, and if they do they are so tangled into the spaghetti and meatballs, that they don't understand a bloody thing.
When you travel and take travel insurance, do you read the 900 page policy ? who does...... DO people read the dozen page software licenses ? you know the fine print that requires 300x zooming so you can barely read ?