News for hackers. Stuff that matters.
Re:Why I’d like a “license type” setting for GitHub projects by mindcrime on Thursday April 05, 2012 @10:53AM (#3802770)
For "GPL type" licenses, it would probably be better to use the term "copyleft" rather than "restrictive" since their copyleft nature is really what's particular about them.

That said, I'd almost prefer a setting that lets you specify the exact license. The problem is, what do you do about dual/multi licensed projects, or projects which contain code that's under a mixture of licenses? I suppose you could argue that it refers to the "dominant" or "main" license, but - to be pedantic - you can't always describe a project as being under one single license.

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.

Re:Why I’d like a “license type” setting for GitHub projects by madrobby on Thursday April 05, 2012 @10:59AM (#3802808)
Many people don't know what "copyleft" is, so "restrictive" makes more sense. There are more restrictions.

For complex situations, you can always choose "other". As stated in my article, this isn't a replacement for a project's LICENSE file.

Re:Why I’d like a “license type” setting for GitHub projects by mindcrime on Thursday April 05, 2012 @11:46AM (#3803068)
Many people don't know what "copyleft" is, so "restrictive" makes more sense.

I could see that holding true among the general population, but among developers? What developer who's going to be browsing Github doesn't know what copyleft means?

There are more restrictions.

Yes and no. Even licenses like the Apache License do impose restrictions of sorts, and the whole "permissive" vs "restrictive" thing is hardly a binary proposition. It's a continuum... and that's not even considering that saying "restrictive" raise the issue of "restrictive for who?" Yes, arguably the GPL is more restrictive in terms of how a developer can interact with GPL'd code, but from an end-user perspective the GPL is "more free" in a sense.

All of that said, I get the point behind a simple binary "restrictive/permissive" flag, and I think most people would intuitively grok the general sense of it. I'm not opposed to it, but I think we could do better.

Hmmm... that raises an interesting point... does Github have any sort of notion of explicit support for DOAP[1] files? Encouraging people to use DOAP files might be a better answer anyway.

[1]: http://en.wikipedia.org/wiki/Description_of_a_Project

Re:Why I’d like a “license type” setting for GitHub projects by nkassis on Thursday April 05, 2012 @04:15PM (#3804402)
"Yes and no. Even licenses like the Apache License do impose restrictions of sorts, and the whole "permissive" vs "restrictive" thing is hardly a binary proposition. It's a continuum... and that's not even considering that saying "restrictive" raise the issue of "restrictive for who?" Yes, arguably the GPL is more restrictive in terms of how a developer can interact with GPL'd code, but from an end-user perspective the GPL is "more free" in a sense."

This is an important point. How many people know that they should list their changes when using EDIT:Some licenses or the patent stuff in the Apache license etc...

These tags don't really make sense.

Re:Why I’d like a “license type” setting for GitHub projects by mindcrime on Thursday April 05, 2012 @04:56PM (#3804588)
or the patent stuff in the Apache license

Exactly. That's a great example of what I had in mind. Nobody talks about it, but that stuff is there and is important.

Re:Why I’d like a “license type” setting for GitHub projects by pygy_ on Thursday April 05, 2012 @11:12AM (#3802873)
Prepare for an uproar if an entity the size of GitHub summarizes the GPL as "restrictive".

The GPL enables freedom for the end user, who's entitled to obtain and modify the source of the programs he uses. It offers some protection against repressive governments and monopolistic companies, a much broader scope than what permissive licenses enable (freedom for the developers).

"Copyleft" is well defined and easy to google. Education doesn't hurt people.

Re:Why I’d like a “license type” setting for GitHub projects by madrobby on Thursday April 05, 2012 @11:28AM (#3802974)
So what if there's an uproar? Other license writers could also want to be treated specially.

This is just about a general filter, into "proprietary", "do whatever you want to", and "restrictive" open source licenses; for developers when they choose which projects on GitHub might be a good fit for their needs.

If you read the GPL it puts a lot of restrictions on what you can do as a developer. So do other licenses (for example licenses that allow you to use the source in open source projects but require some form of payment when used for commercial products).

Re:Why I’d like a “license type” setting for GitHub projects by pygy_ on Thursday April 05, 2012 @12:00PM (#3803146)
> So what if there's an uproar?

It would be boneheaded from a PR stand point, and it is insulting towards the GPL.

> Other license writers could also want to be treated specially.

You seem to have a serious gripe with the GPL. The GPL (its unnamed ancestor, to be pedantic) is the mother of open source licenses. It enables Freedom, with a capital "f" for its users, at the expense of obligations for people who distribute binaries. Liberal licenses turn the situation around.

Labeling the GPL, but not liberal licenses as restrictive is heavily biased, and simply does not reflect reality (since liberal licenses put implicit restrictions on binaries recipients).

I speak as a license author, BTW: https://github.com/pygy/The-Romantic-WTF-Public-License

Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Thursday April 05, 2012 @01:13PM (#3803523)
I'd love to release source, and USE gpl software, and even make a unsigned binary available that if you could hack your own hardware to run, you could. But even if I did, the GPL would prevent me from releasing said software using GPLed libraries, as the actual binary they get has to be trivially copyable. That's crap. That's restrictive. Why can't I supply you with an alternative binary on a website just like I can with the source?

Restrictive isn't hate. It's a description. GPL licensed code is useless code to people who develop for top tier gaming platforms other than the PC.

Re:Why I’d like a “license type” setting for GitHub projects by pygy_ on Thursday April 05, 2012 @01:39PM (#3803636)
> I'd love to release source, and USE gpl software, and even make a unsigned binary available that if you could hack your own hardware to run, you could. But even if I did, the GPL would prevent me from releasing said software using GPLed libraries, as the actual binary they get has to be trivially copyable. That's crap. That's restrictive. Why can't I supply you with an alternative binary on a website just like I can with the source?

I'm afraid I don't understand your point... You can distribute GPLed software as binaries, but you must provide the source on request.

Edit: Perhaps you mean that you want to release your source code under another license?

> Restrictive isn't hate. It's a description.

My point is that all licenses are restrictive in a way or another.

Even WTF-type licenses or the public domain have implicit restrictions.

Singling out the GPL as restrictive is insulting, because its restrictions are designed to enable the freedom for people to check the source code for vulnerabilities or user hostile features (how many backdoors for the US govt. are there in Windows?).

> GPL licensed code is useless code to people who develop for top tier gaming platforms other than the PC.

... because of restrictions imposed by the SDK user agreement.

Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Saturday April 07, 2012 @10:29AM (#3810952)
Section 6 of GPLv2 says:

> Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein.

This is the issue: You HAVE to put Fairplay on the programs (aka, drm, aka, Further Restrictions).

It is not Apple's licensing agreement, but instead the uniform Fairplay system on the device.

This is the same issue on Nintendo, Sony, and Xbox (although some platforms have source provided libraries which likely would have to be GPLed as well, and you can't under NDAs, the uniform DRM makes GPL2 incompatable with those platforms).

GPL3 has changed this area, which I take to be admission of the flaw there. Then again, GPL 3 added a ton of stuff people disliked as well, so it's adoption is less than full.

You can meander back and forth that many licenses are restrictive or not, but the GPL is designed to force certain actions from users of the code. That's fine that they release their code that way, but the fact they're trying to do more then get attribution and not get sued with the license, or even get fixes back for their own parts of the code, means people should be warned about this.

Re:Why I’d like a “license type” setting for GitHub projects by dfox on Thursday April 05, 2012 @01:55PM (#3803722)
GPL actually does not care about binaries, it only stipulates that if you are distributing binaries you have to distribute matching GPL licensed source code with it.

The fact that it implies that you cannot disallow users to produce and distribute additional copies is the whole point of GPL.

Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Saturday April 07, 2012 @08:19PM (#3812565)
GPL 2 does. Look at my response to the sister post to yours.
Re:Why I’d like a “license type” setting for GitHub projects by phillmv on Thursday April 05, 2012 @11:42AM (#3803044)
You do understand how there are people who would disagree with your characterization, and thus the more neutral term 'copyleft' is the most… let's call it politically-safe term to use. Let's not even touch lumping the copyleft licenses with non-commercial-only licenses.

The gradation of rights and privileges goes farther than "Public Domain, Sort of Public Domain, Restrictive".

The best way is to just have a dropdown that lists the name of the license.

Re:Why I’d like a “license type” setting for GitHub projects by kl4m on Thursday April 05, 2012 @12:56PM (#3803445)
It has no restrictions for developers, only for redistributors.
Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Saturday April 07, 2012 @10:30AM (#3810957)
Yes, the GPL (specifically GPL2) is powerful enough to empower users on those systems to never have to worry about using a program with any GPLed code in it.

What a benefit for them.

Re:Why I’d like a “license type” setting for GitHub projects by metamattl on Thursday April 05, 2012 @11:13AM (#3802881)
Even if "restrictive" is misleading?

Copyleft licenses really don't seem to be a problem unless you're trying to make something proprietary?

Unless I'm missing some other restriction...

Re:Why I’d like a “license type” setting for GitHub projects by d0mine on Thursday April 05, 2012 @11:23AM (#3802945)
you could use "keep it free" if "copyleft" is not descriptive enough, though just the name of a license would work best.
Re:Why I’d like a “license type” setting for GitHub projects by mkup on Thursday April 05, 2012 @11:44AM (#3803058)
I don't understand why are you being downvoted, as GPL does actually impose some restrictions in comparison to BSD/MIT.

These restrictions may be for copyleft, for benefit of end users, pro bono, for whatever else, but there are restrictions, and the term "restrictive open source" captures the essense of this license.

Also, these restrictions won't disappear no matter how low your (or mine) comment is downvoted here on HN.

Re:Why I’d like a “license type” setting for GitHub projects by nitrogen on Thursday April 05, 2012 @04:59PM (#3804604)
The problem is, what do you do about dual/multi licensed projects, or projects which contain code that's under a mixture of licenses?

All questions that were answered over a decade ago by sites like SourceForge. Though not perfect, their solution was using tags for each license, and letting developers tag their project with multiple licenses (among other attributes, like language used, development state, etc.). This tagging system was called the Trove system, but since a software company has named itself "Trove Software", my last few Google queries didn't lead me to the origins of the system, only Freshmeat and SourceForge's references to the name.

http://sourceforge.net/apps/trac/sourceforge/wiki/Software%2...

http://freecode.com/articles/fm3s-fresh-features-tagging

Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Thursday April 05, 2012 @01:08PM (#3803492)
They are restrictive: It is impossible to release Apple Mac Appstore or iOS Appstore with them even if you release your source, as the binaries can't even have DRM on them even if you're giving away the source.

The license needs changing. It isn't protecting anyone with the requirement that the binary that someone gets isn't DRMed. There are many software channels (Apple, Xbox, Sony/PS3, Nintendo, just to name a couple big names) that don't have a DRM free way to run them.

Re:Why I’d like a “license type” setting for GitHub projects by HerraBRE on Thursday April 05, 2012 @01:42PM (#3803654)
You've got it backwards. Apple, and anyone else who forces DRM on their users, needs changing.

IMHO. :-)

Re:Why I’d like a “license type” setting for GitHub projects by schrototo on Thursday April 05, 2012 @01:43PM (#3803659)
Isn't that precisely the point of the GPL? To create as much software as possible that cannot be run in DRM environments so that eventually it's the DRM environments that have to die?

It's pretty much a pipe dream of course...

Re:Why I’d like a “license type” setting for GitHub projects by guelo on Thursday April 05, 2012 @01:51PM (#3803698)
This is why we need more indispensable GPL software, to make these jailed sandboxes less palatable.
Re:Why I’d like a “license type” setting for GitHub projects by nknight on Thursday April 05, 2012 @03:39PM (#3804233)
Your gripe seems to be with the restrictive Apple ecosystem, not the GPL.
Re:Why I’d like a “license type” setting for GitHub projects by gte910h on Saturday April 07, 2012 @10:35AM (#3810968)
Sure, I'd happily truthfully label both the GPL and the Apple iOS platform as restrictive.

Many parents love that part of it.