News for hackers. Stuff that matters.
Re:Why I’d like a “license type” setting for GitHub projects by DannyBee on Thursday April 05, 2012 @10:59AM (#3802806)
I would love this, but there are at least a thousand open source licenses. Even if you limit it to licenses that have at least 1% adoption rates, you still have at least 40 (there are more, i just stopped counting).

As such, this would be a confusing dropdown. A free form text field with autocomplete (and synonyms, so if you typed "general public license", it would still autocomplete GPL.

Re:Why I’d like a “license type” setting for GitHub projects by metamattl on Thursday April 05, 2012 @11:22AM (#3802940)
Not really. There's less than 100 licenses out there, and most projects use a subset of around 10 of them.
Re:Why I’d like a “license type” setting for GitHub projects by madrobby on Thursday April 05, 2012 @11:00AM (#3802813)
The drop down has 4 entries. Please read the article again. :)
Re:Why I’d like a “license type” setting for GitHub projects by DannyBee on Thursday April 05, 2012 @11:02AM (#3802830)
Even in that case, he's trying to classify 1000+ open source licenses into 4 categories, which doesn't really work out well without a dictator.

People have different views on what "permissive" is. Even if you told people what they should choose for each license, they will still choose what their ideology says is right about the license.

IE plenty of people will choose "permissive" for GPL.

I've spent an inordinate amount of time classifying licenses into ~4 categories for compliance at Google, so i know where this path leads :) In my case, I can end discussions by fiat and say "this is how it's going to be". When you have 1000+ different project owners who each get to make their own decision, the field will become useless because you won't be able to tell what it really means.

Re:Why I’d like a “license type” setting for GitHub projects by madrobby on Thursday April 05, 2012 @11:08AM (#3802857)
It's actually really simple:

"Permissive": anything that is generally MIT/BSD/WTF/Apache 2.0

"Restrictive": anything that is GPL or requires you to pay for or share all sources

Given that the vast majority of software use only one of a handful of licenses, I think that's a non-issue (tho there may be edge cases, I agree with that). For stuff that is not categorized, people can just put in "other".

(Do you have a list of those classifications btw, that would be useful.)

In general, a setting like this would likely raise awareness of people sharing code that they should choose a license in the first place. Far too many useful pieces of code on GitHub don't come with a license or copyright statement at all.

Re:Why I’d like a “license type” setting for GitHub projects by DannyBee on Thursday April 05, 2012 @11:29AM (#3802980)
Okay, so let's start simple: Where does LGPL fit into these two? (LGPL is in the top 5 licenses, so it's important)

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)

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.

Re:Why I’d like a “license type” setting for GitHub projects by metamattl on Thursday April 05, 2012 @11:18AM (#3802909)
> "Restrictive": anything that is GPL or requires you to pay for or share all sources

Paying for sources, sounds an awful lot like proprietary software. Pay for binaries, sure... sources shouldn't be withheld and should be available for a nominal fee, which in the case of GitHub and others, is $0.

Re:Why I’d like a “license type” setting for GitHub projects by mindcrime on Thursday April 05, 2012 @11:53AM (#3803107)
I would love this, but there are at least a thousand open source licenses. Even if you limit it to licenses that have at least 1% adoption rates, you still have at least 40 (there are more, i just stopped counting).

My personal take would be to limit it to: 1. licenses that are certified by the OSI, and 2. licenses listed as "GPL compatible" by the FSF, assuming that (2) isn't just a subset of (1) anyway.

That would include by far the majority of popular and widely used licenses. Maybe have an "Other" field for anything else?