2013-04-09 12:41:25 -04:00
---
layout: default
class: home
2013-07-13 10:38:53 -04:00
hide_breadcrumbs: true
2015-10-23 17:50:25 -04:00
title: Choosing an open source license doesn’ t need to be scary
2014-01-24 08:25:40 +02:00
permalink: /
2013-04-09 12:41:25 -04:00
---
2013-06-11 12:39:22 -04:00
2013-07-13 15:42:46 -04:00
< h2 >
< span > {< / span >
Which of the following best describes your situation?
< span > }< / span >
< / h2 >
2013-12-09 20:05:34 +02:00
< ul class = "triptych situations clearfix" >
2014-01-23 10:49:36 +02:00
< li class = "whatever" >
2013-09-16 15:16:10 -04:00
< a href = "licenses/mit" >
2013-12-13 19:43:30 +02:00
< span class = "triptych-sprite three-arrows" > < / span >
2013-09-16 15:16:10 -04:00
< h3 > I want it simple and permissive.< / h3 >
< / a >
2013-07-13 15:42:46 -04:00
< p >
2015-01-10 14:20:22 +01:00
The < a href = "licenses/mit" > MIT License< / a > is a permissive license that is short and to the point. It lets people do anything they want with your code as long as they provide attribution back to you and don’ t hold you liable.
2013-07-13 15:42:46 -04:00
< / p >
< p >
2016-01-31 19:53:09 +01:00
< strong > jQuery< / strong > , < strong > Rails< / strong > and < strong > .NET Core< / strong > use the MIT License.
2013-07-13 15:42:46 -04:00
< / p >
< / li >
2013-10-30 20:23:28 +02:00
< li class = "patents" >
2014-09-05 11:47:43 -04:00
< a href = "licenses/apache-2.0/" >
2013-12-13 19:43:30 +02:00
< span class = "triptych-sprite lightbulb" > < / span >
2015-01-10 14:20:22 +01:00
< h3 > I’ m concerned about patents.< / h3 >
2013-09-16 15:16:10 -04:00
< / a >
2013-07-13 15:42:46 -04:00
< p >
2016-02-16 09:29:18 -08:00
The < a href = "licenses/apache-2.0/" > Apache License 2.0< / a > is a permissive license similar to the MIT License, but also provides an express grant of patent rights from contributors to users.
2013-07-13 15:42:46 -04:00
< / p >
< p >
2016-02-16 09:29:18 -08:00
< strong > Apache< / strong > , < strong > Swift< / strong > , and < strong > Android< / strong > use the Apache License 2.0.
2013-07-13 15:42:46 -04:00
< / p >
< / li >
2013-10-30 20:23:28 +02:00
< li class = "copyleft" >
2015-11-17 15:59:59 +01:00
< a href = "licenses/gpl-3.0/" >
2013-12-13 19:43:30 +02:00
< span class = "triptych-sprite circular" > < / span >
2013-09-16 15:16:10 -04:00
< h3 > I care about sharing improvements.< / h3 >
< / a >
2013-07-13 15:42:46 -04:00
< p >
2016-02-16 09:29:18 -08:00
The GNU GPL (< a href = "licenses/gpl-2.0/" > V2< / a > or < a href = "licenses/gpl-3.0/" > V3< / a > ) is a copyleft license that requires anyone who distributes your code or a derivative work to make the source available under the same terms. V3 is similar to V2, but further restricts use in hardware that forbids software alterations.
2013-07-13 15:42:46 -04:00
< / p >
< p >
2016-02-16 09:29:18 -08:00
< strong > WordPress< / strong > , < strong > Linux< / strong > , and < strong > Bash< / strong > use the GNU GPL.
2013-07-13 15:42:46 -04:00
< / p >
< / li >
< / ul >
2013-09-16 15:42:21 -04:00
< h2 >
< span > {< / span >
What if none of these work for me?
< span > }< / span >
< / h2 >
2013-12-09 20:05:34 +02:00
< ul class = "triptych see-more clearfix" >
2014-01-23 10:49:36 +02:00
< li >
2016-02-26 12:34:20 -08:00
< h3 > My project isn’ t software.< / h3 >
2013-09-16 15:17:02 -04:00
< p >
2016-02-26 12:34:20 -08:00
< a href = "non-software" > There are licenses for that< / a > .
2013-09-16 15:17:02 -04:00
< / p >
2013-09-16 15:16:10 -04:00
< / li >
< li >
2013-09-16 15:42:21 -04:00
< h3 > I want more choices.< / h3 >
2013-09-16 15:17:02 -04:00
< p >
2013-09-16 15:47:27 -04:00
< a href = "licenses" > More licenses are available< / a > .
2013-09-16 15:17:02 -04:00
< / p >
2013-09-16 15:16:10 -04:00
< / li >
< li >
2015-01-10 14:20:22 +01:00
< h3 > I don’ t want to choose a license.< / h3 >
2013-09-16 15:17:02 -04:00
< p >
2015-01-10 14:20:22 +01:00
< a href = "no-license" > You don’ t have to< / a > .
2013-09-16 15:17:02 -04:00
< / p >
2013-09-16 15:16:10 -04:00
< / li >
< / ul >