views:

935

answers:

4

Hello,

I am trying to understand various licenses. I usually do small projects in which I use say a jquery plugin which is under MIT license. Now is it okay for me to do the same? Is there a sort of a matrix which compares all the licenses (major ones atleast) and tells me just one thing:

Royalty-free ability to use in commercial project? (no back-links or anything) (I dont mind keeping their copyright text on top of the code)

Thank you very much.

Update Thank you very much for all your answers. Also wondering what exactly do they mean by LGPL i.e. lesser GPL. I read the license, but could not seem to understand what exactly it means.

+1  A: 

For your purposes, you will want to look for BSD or MIT licensed code. GPL is generally not suitable for use in commercial projects (this is a broad generalisation, there are situations where it is appropriate!). CC does not usually apply to software.

I am not a lawyer, and free advice is worth every penny.

Greg Hewgill
Not true. CC can be applied to software, too. (Although I admit the CC licenses are not primarily targeted at the software world.)
DevSolar
Text adjusted. This is why I'm not a lawyer!
Greg Hewgill
+9  A: 

A software license agreement is a contract between a producer and a user of computer software which grants the user a software license. Most often, a software license agreement indicates the terms under which an end-user may utilize the licensed software, in which case the agreement is called an end-user license agreement or EULA. When the software license agreement is between the software licensor and a business or government entity, it is often implemented as a specialized form of contract with many clauses unique to the license and the nature of the software being licensed.

Source: Software license agreement


GPL:

The GNU General Public License (GNU GPL or simply GPL) is a widely used free software license, originally written by Richard Stallman for the GNU project. The GPL is the most popular and well-known example of the type of strong copyleft license that requires derived works to be available under the same copyleft. Under this philosophy, the GPL grants the recipients of a computer program the rights of the free software definition and uses copyleft to ensure the freedoms are preserved, even when the work is changed or added to. This is in distinction to permissive free software licenses, of which the BSD licenses are the standard examples.

Source: GNU General Public License


MIT:

The MIT License is a free software license originating at the Massachusetts Institute of Technology (MIT), used by the MIT X Consortium.

It is a permissive license, meaning that it permits reuse within proprietary software on the condition that the license is distributed with that software. The license is also GPL-compatible, meaning that the GPL permits combination and redistribution with software that uses the MIT License.

According to the Free Software Foundation, the MIT License is more accurately called the X11 license, since MIT has used many licenses for software and the license was first drafted for the X Window System.

Source: MIT License


CC:

Creative Commons licenses are several copyright licenses released on December 16, 2002 by Creative Commons, a U.S. non-profit corporation founded in 2001.

Many of the licenses, notably all the original licenses, grant certain "baseline rights", such as the right to distribute the copyrighted work without changes, at no charge. Some of the newer licenses do not grant these rights.

Creative Commons licenses are currently available in 43 different jurisdictions worldwide, with more than nineteen others under development. Licenses for jurisdictions outside of the United States are under the purview of Creative Commons International.

Source: Creative Commons licenses

M. Jahedbozorgan
+1. A nitpick: copyright licenses for free software are not necessarily contracts or agreements, technically speaking, since the user (receiver of the code) does not need to explicitly agree to them. That rarely matters outside the court room, though.
Lars Wirzenius
You should probably note that Creative Commons are not recommended for software because they say nothing about source code, whereas software licenses were specifically designed for that purpose. Creative Commons licenses are usually more for content, i.e. audio, images, etc.
Chris Lutz
A: 

Especially the GPL is difficult to summarize shortly. I'll try anyway: You can use GPL code in your product royalty-free as long as the code is used stand-alone, e.g. a GPL database or a processing tool. But if your product is "based" on the GPL code, i.e. linked with it and extending its functionality, then your product must be under GPL too.

Being under GPL means everyone using the product must be allowed full access to the source, too, including the right to re-distribute the code, verbatim or modified. While strictly speaking the GPL allows you to charge customers for the product, this effectively means you cannot sell the product for profit. GPL evangelists claim you could sell support or documentation, but I have some issues with that notion I will not elaborate upon here. (First class flaimbait...)

DevSolar
Assume I am making a site like say StackOverflow, and I use a GPL based WYSIWYG editor for posting new topics. Is that allowed?
Alec Smart
AFAIK - Yes, you may. You may have to include some copyright text in your code and packaging - that's it.
Sandy
+3  A: 

The following link http://www.opensource.org/licenses, posts all licences that confirm to the Open Source standard. This means all licences here are royalty free and would not request you for a backlink/ad etc. You may have to keep the copyright files/text in your software.

CC, or Creative Commons (http://creativecommons.org), is about content, one authors, and not generally for the code. It generally applies to documentation or forums like SO. Again there are different versions of CC, but, none of them requires back-links/ads, at max only attribution.

Sandy