News for hackers. Stuff that matters.
Re:Why I’d like a “license type” setting for GitHub projects by jakobe on Thursday April 05, 2012 @11:39AM (#3803034)
No. "Restrictive" vs. "permissive" captures exactly the relevant information. If I look for some code to include in my project, I don't care if the license is "copyleft" or "copyright" or whatever. I just need to know if including the code puts legal restrictions on my project.

For example, both GPL and CC-NC are "restrictive", but GPL is "copyleft" while CC-NC is not.

Also, "copyleft" would somehow suggest compatibility, but this is not the case: GPL and CC-SA are definitely not compatible, so "restrictive" would also be a good adjective in that case.

Re:Why I’d like a “license type” setting for GitHub projects by scott_s on Thursday April 05, 2012 @12:05PM (#3803175)
Those are still biased terms, similar to how people highlight the positive for characterizing their political stances. (I've never met someone who considered themselves "anti-life" or "anti-choice.") Someone could equally say that what you call "restrictive" licenses are "freedom preserving."
Re:Why I’d like a “license type” setting for GitHub projects by jakobe on Thursday April 05, 2012 @01:33PM (#3803615)
I don't understand how anybody can complain that "restrictive" is a bad adjective for a license that contains hundreds of restrictions. "Freedom preserving" sounds a bit like Orwellian double speak.
Re:Why I’d like a “license type” setting for GitHub projects by scott_s on Thursday April 05, 2012 @02:17PM (#3803829)
Consider the other viewpoint: "I don't understand how anyone could complain that a license which ensures that users maintain all freedoms to modify the code as 'restrictive.'"

It's a difference of priorities. Which aspect do you think is more important? You value different things higher than others.

Re:Why I’d like a “license type” setting for GitHub projects by lmm on Thursday April 05, 2012 @12:02PM (#3803157)
The BSD license prohibits you from falsely claiming authorship of the code it covers, so I guess that's going to be filed under "restrictive" too?

Licenses are complicated, and what people want to do with code is complicated too; "restrictive" vs. "permissive" cannot be defined well. "copyleft" represents a well-defined, understandable concept; while not without edge cases, it makes it fairly clear what kind of license we're talking about.

Re:Why I’d like a “license type” setting for GitHub projects by jakobe on Thursday April 05, 2012 @12:23PM (#3803275)
It might be difficult to find a formal and logically coherent definition of "restrictive" vs. "permissive", but I was thinking in more pragmatic terms. Like with porn, "I know it when I see it". As I see it, required attribution somewhere in the docs is not very restrictive. On the other hand, 20 pages of legal mumbo jumbo concerning distribution are restrictive.
Re:Why I’d like a “license type” setting for GitHub projects by Natsu on Thursday April 05, 2012 @04:13PM (#3804392)
> "I know it when I see it"

Categories which are dependent on the user's own viewpoint are not suitable for a wide audience because the people are too different.