Here is a useful breakdown of the different software licenses. Jeff Atwood's Coding Horror blog does a great job explaining each license type.
Name: None | Source: Open | Type (Clauses): None
Without a license, the code is copyrighted by default. People can read the code, but they have no legal right to use it. To use the code, you must contact the author directly and ask permission.
Name: Public domain | Source: Open | Type (Clauses):Permissive (0)
If your code is in the public domain, anyone may use your code for any purpose whatsoever. Nothing is in the public domain by default; you have to explicitly put your work in the public domain if you want it there. Otherwise, you must be dead a long time before your work reverts to the public domain.
Name: GPL | Source: Open | Type (Clauses):Copyleft (12)
The archetypal bearded, sandal-clad free software license. Your code can never be used in any proprietary program, ever! Take that, capitalism!
Name: LGPL | Source: Open | Type (Clauses):Mostly Copyleft (16)
GPL with a cleverly-constructed pressure valve release. Your free software can be binary linked to proprietary programs under certain very specific circumstances.
Name: MIT/X11 | Source: Open | Type (Clauses):Permissive (2)
Short and sweet. Includes generic legal disclaimer of liability.
Name: BSD | Source: Open | Type (Clauses):Permissive (2)
Short and sweet. Includes legal disclaimer of liability with explicitly named organization.
Name: Apache | Source: Open | Type (Clauses):Permissive (9)
Requires derivative works to provide notification of any licensed or proprietary code in a common location.
Name: Eclipse | Source: Open | Type (Clauses):Permissive (7)
Business friendly. Allows derivative works to choose their own license for their contributions.
Name: Mozilla | Source: Open | Type (Clauses):Weak Copyleft (13)
Allows liberal mixing with proprietary software.
Name: MS Permissive | Source: Open | Type (Clauses):Permissive (3)
Resembles the MIT and BSD licenses. Not formally accepted by OSI, and also offered in a "Windows-only" LPL variant.
Name: MS Community | Source: Open | Type (Clauses):Copyleft (3)
Resembles the GPL license. Requires all contributed code to be returned to the community. Not formally accepted by OSI, and also offered in a "Windows-only" LCL version.
Name: MS Reference | Source: Proprietary | Type (Clauses):Read Only (3)
You can review the code, or make copies of it, but you can't use it or change it in any way. Allows a window (no pun intended) on formerly completely proprietary, secret code.
Helpful Link
If you do not have a software license template to use, take a look at what Binpress's license generator. I am not a Binpress employee. I came across their tool and found it useful.
Yes, you simply need to use multi-licensing to distribute your software under two or more different sets of terms and conditions. There are a number of products using this approach, one of the good examples is MySQL.
您可以要求您的客户/被许可人在 GNU GPL、知识共享非商业性相同方式共享或任何您认为合适的许可证下使用您的软件。
When you are the copyright owner, you can define the terms of use much to your liking...
You could require your customers / licensees to use your software under a license such as GNU GPL, Creative Commons NonCommercial ShareAlike or anything you deem appropriate.
It's a typical case when license templates will not help you much.
Because you don't want to write your own license youself, or worse, copy/paste paragraphs you don't understand from the templates, you really need to hire a lawyer if you are serious in doing business in software.
发布评论
评论（4）
许可证信息
以下是不同软件许可证的有用细分。 Jeff Atwood 的 Coding Horror 博客 很好地解释了每种许可证类型。
姓名：无 |来源：开放|类型（子句）：无
没有许可证，代码默认受版权保护。人们可以阅读代码，但他们没有使用它的合法权利。要使用该代码，您必须直接联系作者并征求许可。
名称：公共域 |来源：开放 |类型（子句）：宽容 (0)
如果您的代码位于公共领域，任何人都可以将您的代码用于任何目的。默认情况下，没有任何内容属于公共领域；如果您希望将您的作品置于公共领域，则必须明确将其置于公共领域。否则，在你的作品重新进入公共领域之前，你必须已经死了很长一段时间。
名称：GPL |来源：开放|类型（条款）：Copyleft (12)
典型的留着胡子、穿着凉鞋的自由软件许可证。您的代码永远不能在任何专有程序中使用！接受这个，资本主义！
名称：LGPL |来源：开放|类型（条款）：主要是 Copyleft (16)
GPL，带有构造巧妙的压力阀释放装置。在某些非常特定的情况下，您的自由软件可以二进制链接到专有程序。
名称：MIT/X11 |来源：开放|类型（子句）：宽容型（2）
简短而甜蜜。包括一般法律免责声明。
名称：BSD |来源：开放 |类型（子句）：宽容型（2）
简短而甜蜜。包括明确指定组织的法律免责声明。
名称：Apache |来源：开放 |类型（条款）：宽容 (9)
要求衍生作品在公共位置提供任何许可或专有代码的通知。
名称：Eclipse |来源：开放 |类型（子句）：宽容 (7)
商业友好。允许衍生作品为其贡献选择自己的许可证。
名称：Mozilla |来源：开放 |类型（子句）：Weak Copyleft (13)
允许与专有软件自由混合。
名称：MS Permissive |来源：开放 |类型（子句）：Permissive (3)
类似于 MIT 和 BSD 许可证。未被 OSI 正式接受，并且还以“仅限 Windows”的 LPL 变体形式提供。
名称：MS 社区 |来源：开放 |类型（子句）：Copyleft (3)
类似于 GPL 许可证。要求将所有贡献的代码返回给社区。未被 OSI 正式接受，并且还提供“仅限 Windows”LCL 版本。
名称：MS 参考 |来源：专有|类型（子句）：只读 (3)
您可以查看代码或复制代码，但不能以任何方式使用或更改它。允许对以前完全专有的秘密代码打开一个窗口（没有双关语的意思）。
有用的链接
如果您没有可用的软件许可证模板，请查看 Binpress 的许可证 生成器。我不是 Binpress 员工。我偶然发现了他们的工具并发现它很有用。
License Information
Here is a useful breakdown of the different software licenses. Jeff Atwood's Coding Horror blog does a great job explaining each license type.
Name: None | Source: Open | Type (Clauses): None
Without a license, the code is copyrighted by default. People can read the code, but they have no legal right to use it. To use the code, you must contact the author directly and ask permission.
Name: Public domain | Source: Open | Type (Clauses):Permissive (0)
If your code is in the public domain, anyone may use your code for any purpose whatsoever. Nothing is in the public domain by default; you have to explicitly put your work in the public domain if you want it there. Otherwise, you must be dead a long time before your work reverts to the public domain.
Name: GPL | Source: Open | Type (Clauses):Copyleft (12)
The archetypal bearded, sandal-clad free software license. Your code can never be used in any proprietary program, ever! Take that, capitalism!
Name: LGPL | Source: Open | Type (Clauses):Mostly Copyleft (16)
GPL with a cleverly-constructed pressure valve release. Your free software can be binary linked to proprietary programs under certain very specific circumstances.
Name: MIT/X11 | Source: Open | Type (Clauses):Permissive (2)
Short and sweet. Includes generic legal disclaimer of liability.
Name: BSD | Source: Open | Type (Clauses):Permissive (2)
Short and sweet. Includes legal disclaimer of liability with explicitly named organization.
Name: Apache | Source: Open | Type (Clauses):Permissive (9)
Requires derivative works to provide notification of any licensed or proprietary code in a common location.
Name: Eclipse | Source: Open | Type (Clauses):Permissive (7)
Business friendly. Allows derivative works to choose their own license for their contributions.
Name: Mozilla | Source: Open | Type (Clauses):Weak Copyleft (13)
Allows liberal mixing with proprietary software.
Name: MS Permissive | Source: Open | Type (Clauses):Permissive (3)
Resembles the MIT and BSD licenses. Not formally accepted by OSI, and also offered in a "Windows-only" LPL variant.
Name: MS Community | Source: Open | Type (Clauses):Copyleft (3)
Resembles the GPL license. Requires all contributed code to be returned to the community. Not formally accepted by OSI, and also offered in a "Windows-only" LCL version.
Name: MS Reference | Source: Proprietary | Type (Clauses):Read Only (3)
You can review the code, or make copies of it, but you can't use it or change it in any way. Allows a window (no pun intended) on formerly completely proprietary, secret code.
Helpful Link
If you do not have a software license template to use, take a look at what Binpress's license generator. I am not a Binpress employee. I came across their tool and found it useful.
是的，您只需使用多重许可即可将您的软件分发给两个或多个不同的条款和条件集。有许多产品使用这种方法，MySQL 就是一个很好的例子。
Yes, you simply need to use multi-licensing to distribute your software under two or more different sets of terms and conditions. There are a number of products using this approach, one of the good examples is MySQL.
当您是版权所有者时，您可以根据自己的喜好定义使用条款...
您可以要求您的客户/被许可人在 GNU GPL、知识共享非商业性相同方式共享或任何您认为合适的许可证下使用您的软件。
When you are the copyright owner, you can define the terms of use much to your liking...
You could require your customers / licensees to use your software under a license such as GNU GPL, Creative Commons NonCommercial ShareAlike or anything you deem appropriate.
这是许可证模板对您没有多大帮助的典型情况。
因为您不想自己编写许可证，或者更糟糕的是，从模板中复制/粘贴您不理解的段落，如果您认真开展业务，您确实需要聘请律师在软件中。
It's a typical case when license templates will not help you much.
Because you don't want to write your own license youself, or worse, copy/paste paragraphs you don't understand from the templates, you really need to hire a lawyer if you are serious in doing business in software.