Re:Why I’d like a “license type” setting for GitHub projects
by mindcrime on Thursday April 05, 2012 @11:56AM
(#3803122)
Right, and likewise for the MPL, which is a sort of copyleft license, but is generally considered "weak copyleft" unlike the GPL, which is "strong copyleft."[1]
[1]: http://en.wikipedia.org/wiki/Copyleft#Strong_and_weak_copyle...
Re:Why I’d like a “license type” setting for GitHub projects
by gte910h on Thursday April 05, 2012 @01:15PM
(#3803536)
Restrictive is primarily the case because they don't allowed DRM binaries to be used. The LGPL doesn't have that flaw.
You can't use GPLed code on Apple, Nintendo, Sony or Microsoft gaming platforms due to the binary copy restriction.
So, vast majority depends on how you look at it.
If you are talking about organized software projects, yes, the vast majority use about 20 licenses (I cut off the count at 90%)
If you are talking about code that is out there and has a license marking, "Other" is the #3 category, and we classify over 1000 licenses. (I hand check a lot of these, and only about 1% are classification errors, not really licensed, or munged).
So as you can see, the story is not great, particularly for people who want to just take pieces of code.
Don't get me wrong, I absolutely and completely agree that things should be marked with licenses and give people some idea of what they can do. I'm just saying doing it usefully is not as simple as giving people 2-4 categories and saying "have at it!"
As for the categories we have, our categories are based on what would be required if the source is used in a product shipping outside of Google. The categories have been mentioned publicly before, so i'll mention that they are "notice", "reciprocal", "restricted", and "use by exception only" (IE you can only use it if you talk to us first)