Gist 的默认许可证
The default license of a Gist
我想知道在 public gist 中使用代码是否合法，因为 Gist 没有许可证。
我无法在线找到有关 public Gists 的任何许可信息。
根据 https://softwareengineering.stackexchange.com/a/26607/354680，版权默认适用，合理使用除外。我引用一段话有些讽刺意味：
“明确提及您作品的版权在过去是一项义务。现在不再需要了。
“如果你所在的国家是伯尔尼公约的成员，那么它是自动的。你对你的作品拥有全部权利。
"The only exception to this is when your work is used in the context of "合理使用”。例如，我可以 copy/paste 来自互联网或书籍的部分文本来说明我解释的内容。这就是我现在要做的，我我无所畏惧...
"'版权并不禁止所有复制或复制。在美国，合理使用原则，由 1976 年的版权法编纂为 17 U.S.C。§ 107 允许某些复制和分发，而无需版权所有者的许可或付款。该法规没有明确定义合理使用，而是给出了在合理使用分析中要考虑的四个非排他性因素。
这是来自维基百科。'
“但是，未明确提及版权可能会使一些公司不太了解他们善意使用您的代码的权利和义务。
“你想避免所有的书面工作来迫使他们停止使用你的代码，所以作为一般规则，即使这不是义务：
"Add copyright statement in each source code file. Attach the full license to the project."
Jeff Luszcz 的这篇博客 post Getting the Gist of GitHub Gist Licensing 很好地阐明了 gists 用户的许可问题：
The most helpful and accurate way for a Gist author to declare their license is to put the license text in the source on the Gist itself. Typically this would be at the top of the file in a comment block and would contain the copyright date and owner if required by the license.
. . .
In some cases the Gist author places a note somewhere in their GitHub site or homepage that declares the default license for their Gists. They may use text such as “The default license for all public Gists I publish is the following:” and then put the name or text of the license.
. . .
If a file, snippet or other content does not have a declared license, it is a good practice to reach out to the original author and ask what license the content is available under.
我想知道在 public gist 中使用代码是否合法，因为 Gist 没有许可证。 我无法在线找到有关 public Gists 的任何许可信息。
根据 https://softwareengineering.stackexchange.com/a/26607/354680，版权默认适用，合理使用除外。我引用一段话有些讽刺意味：
“明确提及您作品的版权在过去是一项义务。现在不再需要了。
“如果你所在的国家是伯尔尼公约的成员，那么它是自动的。你对你的作品拥有全部权利。
"The only exception to this is when your work is used in the context of "合理使用”。例如，我可以 copy/paste 来自互联网或书籍的部分文本来说明我解释的内容。这就是我现在要做的，我我无所畏惧...
"'版权并不禁止所有复制或复制。在美国，合理使用原则，由 1976 年的版权法编纂为 17 U.S.C。§ 107 允许某些复制和分发，而无需版权所有者的许可或付款。该法规没有明确定义合理使用，而是给出了在合理使用分析中要考虑的四个非排他性因素。 这是来自维基百科。'
“但是，未明确提及版权可能会使一些公司不太了解他们善意使用您的代码的权利和义务。
“你想避免所有的书面工作来迫使他们停止使用你的代码，所以作为一般规则，即使这不是义务：
"Add copyright statement in each source code file. Attach the full license to the project."
Jeff Luszcz 的这篇博客 post Getting the Gist of GitHub Gist Licensing 很好地阐明了 gists 用户的许可问题：
The most helpful and accurate way for a Gist author to declare their license is to put the license text in the source on the Gist itself. Typically this would be at the top of the file in a comment block and would contain the copyright date and owner if required by the license.
. . .
In some cases the Gist author places a note somewhere in their GitHub site or homepage that declares the default license for their Gists. They may use text such as “The default license for all public Gists I publish is the following:” and then put the name or text of the license.
. . .
If a file, snippet or other content does not have a declared license, it is a good practice to reach out to the original author and ask what license the content is available under.