Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

The Open Source Initiative lists 9 different licenses in their list of "License that are popular and widely used or with strong communities".

I want to license my project as open-source. Unfortunately, I do not speak legalese. Is there some chart I could consult that will help me make the right choice, or at least point me in the right direction? For example a table summarizing the differences between the licenses, or perhaps a flow-graph using my requirements to guide me into the correct license for me?

I also intend to meet a lawyer, but any information to start with will help.

share|improve this question

closed as off-topic by ChrisF Sep 18 at 12:13

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking us to recommend a tool, library or favorite off-site resource are off-topic for Programmers as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." – ChrisF
If this question can be reworded to fit the rules in the help center, please edit the question.

2  
2  
License Chooser It lets you choose a license for you project based on certain criteria. –  Mahmoud Hossam May 6 '12 at 0:50
    
I'm not a lawyer either so when I wanted a license for a new application I'm working on I just wrote one myself. Who knows if it would ever really hold up in court, but it is pretty straightforward in explaining what I want done/not done with the code... davidvhill.com/article/an-open-source-license-in-plain-english –  David Hill Mar 22 '13 at 16:58
    
Github have created this simplified site to help users choose a licence: choosealicense.com –  ltn100 Aug 16 at 14:56

4 Answers 4

up vote 28 down vote accepted

Jeff Atwood has done a pretty good job explaining the differences among the multitude of Open Source software licenses in plain English here:

http://www.codinghorror.com/blog/2007/04/pick-a-license-any-license.html

The most important consideration affecting your decision will be your redistribution terms. That is, will you allow your code to be used in commercial applications and if so, will you require such applications to open-source their own code?

This is where the GPL is notable: If you license your code under the GPL, anyone using your code must also license their code under the GPL. Since the GPL requires that all of your code be open-source, this pretty much excludes its use in companies that wish to keep their code proprietary.

Note that the GPL does allow you to use GPL'd code for in-house business applications, so long as you do not redistribute those applications to a third party.

See Also
http://haacked.com/archive/2007/04/04/there-are-only-four-software-licenses.aspx

share|improve this answer
2  
+1 for sharing Jeff Atwood article! –  topgun_ivard Sep 1 '11 at 18:48
4  
Jeff's advice has some errors in it! In many jurisdictions you can not put your work into the public domain (other than by being dead for the requisite amount of time) and it also doesn't mention your point about GPL for code you don't release, for which I'd mention server code, which is a very important model in the industry –  jk. May 6 '12 at 7:46

As you have asked for a chart of Open source licenses comparison:
enter image description here
http://www.bitsandbuzz.com/article/which-open-source-license/

Please, read this excellent article too: Adopting an Open Source Approach to Software Development, Distribution, and Licensing.

share|improve this answer
    
can't access URL at where the recommended article is located: opensource.sys-con.com/node/318776 - consider updating to account for that (brief article summary or its key points would be of great help to readers of this answer). Recommended reading: Are answers that just contain links elsewhere really “good answers”? –  gnat Sep 18 at 8:49
    
That link is deleted by its owner, here are more links: 1. gnu.org/licenses/license-list.html 2. blogs.oracle.com/davidleetodd/entry/… –  Badar Sep 25 at 6:06

A great resource for understanding open source licenses is the very comprehensive, interactive license differentiator, from Oxford Universities OSS Watch.

This asks questions which guide you towards a suitable license for your software.

There are pro's and cons to each, so read up on what restrictions they place on the code and decide who you want to be able to use it. Warning, whichever you choose someone will complain - this is holy war territory, and beyond the scope of this question.

share|improve this answer

There's a simplified explanation for many licenses available on NRecursions (there are more licenses on the blog. Listed a few below).

  • Copyleft license: You can use, modify and distribute the license under the same or equivalent license, but you should also share the source code.
  • Berkely Software Distribution license (BSD): You can combine the software with your proprietary software and release it under a proprietary license, but you have to retain the BSD license text and notices. This license may also have one or two more clauses about using the author's name or advertising.
  • Gnu Public License (GPL): You can use, modify and distribute the software for free or for a fee, but you have to also distribute the source code with it, and if the software is combined with other software, that software will also have to be released as GPL, unless it is not an aggregate (it does not interact with the GPL software)
  • Lesser Gnu Public License (LGPL): Same as GPL, but you're allowed to link your proprietary software with LGPL software and release it under your terms. But there are some conditions under which you can do so.
  • Affero Gnu Public License (AGPL): Same as GPL, but it additionally says that your software is considered as having been distributed, if someone else is able to use it (like if you keep it on a server and they can run it from the server).
  • Massachusetts Institute of Technology license (MIT): You are allowed to use, modify and distribute copies of the software as long as you allow the same rights to the person to whom you distribute the software
  • Apache License: If you follow the Apache license, you're allowed to use, modify and distribute copies of the software, and you can add your own copyright statement to the changes you make. You can also provide additional or different license terms and conditions for use, reproduction or distribution of your modifications.
  • Mozilla Public License (MPL): You can use, modify, distribute and sell the software, provided you also give the recipient the source code. You can also sub-license the modified work, provided you don't restrict the recipients rights to the source code.
share|improve this answer

protected by gnat Aug 16 at 11:29

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.