是否有哪个OSS许可证与哪个OSC许可证兼容的图表? [英] Is there a chart of which OSS License is compatible with which?
问题描述
我对单个OSS许可证有很好的了解，但是当我想在不同许可证下使用代码时，总是会遇到麻烦. BSD与Ms-PL，Apache 2与GPLv3等.
是否有某种配合表"列出了哪些许可证与哪些许可证兼容?
自由软件基金会维护了 Free-Libre /David Wheeler提供的/开源软件(FLOSS)许可证幻灯片(如下所示).箭头表示可以将两个许可证组合在一起，并且可以将合并后的工作视为在箭头的末尾具有许可证，并且可能在箭头的开始处对许可证施加了一些其他限制.
以下段落是该主题的通称，与您的问题相关但不直接相关
确定许可证兼容性的困难以及仅在理解各种许可条款的后果方面的困难就是为什么许可证激增如此糟糕的原因.请，请尽可能使用通用的，易于理解的许可证，例如GPL，LGPL，BSD 2条款或3条款，MIT/X联盟许可证或公共领域专用许可证.无论您做什么，都不要发明自己的许可证.如果必须，请使用与您正在参与的项目通用的许可证，以保持与该项目中其余代码的兼容性.如果遵循这些规则，将有助于减少混乱并提高许可证兼容性.
I have a fairly good understanding of individual OSS licenses, but I always have trouble when I want to use code under different licenses. BSD vs. Ms-PL, Apache 2 vs. GPLv3 etc.
Is there some sort of "mating chart" that lists which licenses are compatible with which ones?
The Free Software Foundation maintains a list of licenses, categorized as GPL compatible, GPL incompatible, and non-free. This can help answer the most common question, which is whether a license is GPL compatible. Since there aren't many other free software licenses which require that the entire derived work be distributed under the same license like the GPL does, compatibility issues are usually lower between other licenses as long as the code stays in distinct libraries or source files.
As far as the Ms-PL goes, you can probably use the FSF list to determine compatibility for that as well. The Ms-PL is a (very) weak-copyleft license (the Ms-RL is slightly stronger, but is still categorized as weak-copyleft). This means that code distributed under it must remain under it, thus making it GPL incompatible, but that you can generally link it to code under permissive or other weak copyleft licenses, as long as you follow the terms of each license and the separately licensed code reside in separate libraries. The only licenses it is likely to be incompatible with are strong copyleft licenses, like the GPL and AGPL. (Standard disclaimer: I am not a lawyer, and this is not legal advice. If you need legal advice, you should talk to a qualified attorney).
For a more limited set of licenses, you can check out this Free-Libre / Open Source Software (FLOSS) License Slide by David Wheeler (reproduced below). Arrows indicate that two licenses may be combined, and that the combined work can effectively be treated as having the license at the end of the arrow, possibly with some additional restrictions taken from the license at the start of the arrow.
the following paragraph is a generic rant on this topic, related but not directly relevant to your question
The difficulty of determining license compatibility, and simply in understanding the ramifications of various licensing terms, is why license proliferation is such a bad thing. Please, please try to use a common, well understood license, such as the GPL, LGPL, BSD 2-clause or 3-clause, MIT/X consortium license, or public domain dedication, if at all possible. Whatever you do, don't invent your own license. If you must, use the license that is common for the project you are contributing to, to maintain compatibility with the rest of the code in that project. If you follow these rules, you will help reduce confusion, and improve license compatibility.
这篇关于是否有哪个OSS许可证与哪个OSC许可证兼容的图表?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
