What you want is something likely compatible with the GNU/GPL license. In particular, the Artistic 2.0 license looks like a good candidate as it looks as if it meets the authorship requirements.
多重许可证是最好的，尽管有点令人困惑。 如果有人正在编写商业代码库，有时出于法律或公司政策的原因，他们在没有获得您的商业许可的情况下无法使用您的代码。 MySQL 是在 2 个许可证下提供的代码库的示例。
有人应该用“我不是律师，律师都是混蛋”来取代“我不是律师”的样板。
License compatibility will be the most important criteria. You may dislike every clause of the a commercial license (for which there is no standard) or the GPL or what have you, but because they are both extremely common, you will want to pick a license that is compatible with them. The CDDL is a beautiful license that is not as compatible as it could be with common licenses.
In the GPL world, LGPL is more compatible than GPL with other code. In the commercial world, the various "Don't sue me if it goes wrong" licenses are the most compatible, e.g. MIT, etc.
Mutliple licenses are best of all, albeit somewhat confusing. If someone is writing a commercial code base, sometimes for legal or company policy reasons, they can't use your code without getting a commercial license from you. MySQL is an example of code base offered under 2 licenses.
Someone should replace the "I'm not a lawyer" boilerplate with "I'm not a lawyer and lawyers are jerks".
Wikipedia has an excellent comparison article which goes over a variety of software licenses, and you should review it carefully, as well as the actual license texts once you have it narrowed down to a few licenses.
The LGPL will fufil clauses 1, 2, and 3 of your request. Clause 4 isn't something that should ideally be covered by a license, but rather by a trademark with an accompanying trademark policy. (registered or un-) See for example Mozilla's Trademark Policy.
发布评论
评论（3）
您可能希望查看以下比较图表：
更小但更简单：
（我不是律师...）
您想要的是可能与GNU/GPL 许可证。 特别是，Artistic 2.0 许可证看起来像是一个很好的候选者，因为它看起来似乎满足作者身份要求。
You may wish to look at this comparison chart:
A little smaller but simpler:
(I am not a lawyer...)
What you want is something likely compatible with the GNU/GPL license. In particular, the Artistic 2.0 license looks like a good candidate as it looks as if it meets the authorship requirements.
许可证兼容性将是最重要的标准。 您可能不喜欢商业许可证（没有标准）或 GPL 或您拥有的其他许可证的每个条款，但因为它们都非常常见，所以您会想要选择与它们兼容的许可证。 CDDL 是一个漂亮的许可证，但与通用许可证的兼容性较差。
在GPL世界中，LGPL比GPL与其他代码更兼容。 在商业世界中，各种“如果出错就不要起诉我”许可证是最兼容的，例如MIT等。
多重许可证是最好的，尽管有点令人困惑。 如果有人正在编写商业代码库，有时出于法律或公司政策的原因，他们在没有获得您的商业许可的情况下无法使用您的代码。 MySQL 是在 2 个许可证下提供的代码库的示例。
有人应该用“我不是律师，律师都是混蛋”来取代“我不是律师”的样板。
License compatibility will be the most important criteria. You may dislike every clause of the a commercial license (for which there is no standard) or the GPL or what have you, but because they are both extremely common, you will want to pick a license that is compatible with them. The CDDL is a beautiful license that is not as compatible as it could be with common licenses.
In the GPL world, LGPL is more compatible than GPL with other code. In the commercial world, the various "Don't sue me if it goes wrong" licenses are the most compatible, e.g. MIT, etc.
Mutliple licenses are best of all, albeit somewhat confusing. If someone is writing a commercial code base, sometimes for legal or company policy reasons, they can't use your code without getting a commercial license from you. MySQL is an example of code base offered under 2 licenses.
Someone should replace the "I'm not a lawyer" boilerplate with "I'm not a lawyer and lawyers are jerks".
维基百科有一篇出色的比较文章，其中介绍了各种软件许可证，您应该查看它仔细阅读，以及将其范围缩小到几个许可证后的实际许可证文本。
LGPL 将满足您请求的第 1、2 和 3 条。 理想情况下，第 4 条不应由许可证涵盖，而应由带有随附商标政策的商标涵盖。 （注册或未注册）例如，请参阅 Mozilla 的商标政策。
当然是 IANAL、IANYL、YMMV 和 OIMACTTA。
Wikipedia has an excellent comparison article which goes over a variety of software licenses, and you should review it carefully, as well as the actual license texts once you have it narrowed down to a few licenses.
The LGPL will fufil clauses 1, 2, and 3 of your request. Clause 4 isn't something that should ideally be covered by a license, but rather by a trademark with an accompanying trademark policy. (registered or un-) See for example Mozilla's Trademark Policy.
Of course, IANAL, IANYL, YMMV, and OIMACTTA.