I love the GPL, but I have a simple rule for my own projects:
The Code should be at least one order of magnitude longer than the license
If your code is just as long as the GPL, there probably is not that much stuff in it that an evil corporation could steal, even if you license it under the MIT X11 License.
As for the question of Public Domain: I live in Germany, where the only legal way to put something in the Public Domain is to commit suicide and wait 70 years (and hope that copyright protection time doesn't get increased between now and 2080). Which is a commitment I am not wanting to make :-) So, I don't really think about that.
You can share anything under the GPL. "Hello World", even. It's a philosophical choice. If you don't mind someone taking these small scripts and redistributing them as closed source, make 'em public domain. If you do mind, make them GPL or something similar.
因此，如果您希望接收者拥有基本的软件自由，并且知道其他人无法合法阻止这一点，那么实现这一目标的唯一方法就是选择自由软件许可证并有效地授予它。 GNU GPL 就如何将其应用到作品中给出了很好的指导。
It doesn't matter how trivial you believe the work to be; the question is whether it falls under copyright restriction or not. The default assumption is that yes, any creative work falls under copyright in just about any jurisdiction.
That's the same for a big program, a small script, an orchestral arrangement, or a sketch on a napkin.
In the absence of an explicit, effective grant of license, all rights are reserved to the copyright holder, which is you if you wrote it. So, like it or not, the burden of what freedoms to grant to others falls on your shoulders.
So, if you want recipients to have the essential software freedoms and know that others cannot legally block that, the only way to make that happen is to choose a free-software license and grant it effectively. The GNU GPL gives good instruction on how to apply it to a work.
If you donate them to the public domain, you're giving up any rights to their ownership, and you're allowing anyone to use, modify, or sell them however they please.
If you release them under GPL, you can also allow anyone to use, modify, or sell them, but you're also explicitly requiring them to provide the same unrestricted use to all "downstream" users. The spirit of GPL is that anyone who passes GPL software to anyone else must also provide the original rights and freedoms to use and further modify that software.
Disclaimer: This is my understanding of GPL, not legal advice. Dammit, Jim, I'm an engineer, not a lawyer.
Scripts are programs, and if you order programming languages based on how abstract they are, bash would be high in the ordering. It is valid to license bash code, and GPL is a fine choice.
发布评论
评论（6）
我喜欢 GPL，但我对自己的项目有一个简单的规则：
如果您的代码与 GPL 一样长，那么即使您根据 MIT X11 获得许可，其中可能也没有那么多东西可供邪恶公司窃取执照。
至于公有领域的问题：我住在德国，在那里将某些东西放入公有领域的唯一合法方式就是自杀并等待70年（并希望版权保护时间不会延长）从现在到 2080 年会增加）。这是我不想做出的承诺:-) 所以，我并没有真正考虑这一点。
I love the GPL, but I have a simple rule for my own projects:
If your code is just as long as the GPL, there probably is not that much stuff in it that an evil corporation could steal, even if you license it under the MIT X11 License.
As for the question of Public Domain: I live in Germany, where the only legal way to put something in the Public Domain is to commit suicide and wait 70 years (and hope that copyright protection time doesn't get increased between now and 2080). Which is a commitment I am not wanting to make :-) So, I don't really think about that.
您可以在 GPL 下共享任何内容。甚至是“你好世界”。这是一个哲学选择。如果您不介意有人获取这些小脚本并将其作为闭源代码重新分发，请将其设为公共领域。如果你介意的话，可以将它们设为 GPL 或类似的东西。
You can share anything under the GPL. "Hello World", even. It's a philosophical choice. If you don't mind someone taking these small scripts and redistributing them as closed source, make 'em public domain. If you do mind, make them GPL or something similar.
无论你认为这项工作有多么琐碎，都没关系。问题是它是否受到版权限制。默认假设是，是的，任何创意作品在几乎任何司法管辖区都受版权保护。
对于大型节目、小型剧本、管弦乐编曲或餐巾纸上的草图来说都是如此。
在没有明确、有效授予许可的情况下，所有权利均归版权所有者所有，如果是您编写的，那么版权所有者就是您。因此，无论你喜欢与否，给予他人哪些自由的重担落在了你的肩上。
因此，如果您希望接收者拥有基本的软件自由，并且知道其他人无法合法阻止这一点，那么实现这一目标的唯一方法就是选择自由软件许可证并有效地授予它。 GNU GPL 就如何将其应用到作品中给出了很好的指导。
It doesn't matter how trivial you believe the work to be; the question is whether it falls under copyright restriction or not. The default assumption is that yes, any creative work falls under copyright in just about any jurisdiction.
That's the same for a big program, a small script, an orchestral arrangement, or a sketch on a napkin.
In the absence of an explicit, effective grant of license, all rights are reserved to the copyright holder, which is you if you wrote it. So, like it or not, the burden of what freedoms to grant to others falls on your shoulders.
So, if you want recipients to have the essential software freedoms and know that others cannot legally block that, the only way to make that happen is to choose a free-software license and grant it effectively. The GNU GPL gives good instruction on how to apply it to a work.
如果您将它们捐赠给公共领域，则表示您放弃了其所有权的任何权利，并且允许任何人随心所欲地使用、修改或出售它们。
如果您根据 GPL 发布它们，您还可以允许任何人使用、修改或出售它们，但您也明确要求他们向所有“下游”用户提供相同的无限制使用。 GPL 的精神是，任何人将 GPL 软件传递给其他人时，也必须提供使用和进一步修改该软件的原始权利和自由。
免责声明：这是我对 GPL 的理解，并非法律建议。该死，吉姆，我是工程师，不是律师。
If you donate them to the public domain, you're giving up any rights to their ownership, and you're allowing anyone to use, modify, or sell them however they please.
If you release them under GPL, you can also allow anyone to use, modify, or sell them, but you're also explicitly requiring them to provide the same unrestricted use to all "downstream" users. The spirit of GPL is that anyone who passes GPL software to anyone else must also provide the original rights and freedoms to use and further modify that software.
Disclaimer: This is my understanding of GPL, not legal advice. Dammit, Jim, I'm an engineer, not a lawyer.
脚本是程序，如果您根据编程语言的抽象程度对它们进行排序，那么 bash 的排名会很高。 bash 代码的许可是有效的，GPL 是一个不错的选择。
Scripts are programs, and if you order programming languages based on how abstract they are, bash would be high in the ordering. It is valid to license bash code, and GPL is a fine choice.
只要您的新许可证类型不违反 BASH 附带的许可证条件，就可以了:-)
As long as your new license type does not violate the conditions of the license that comes along with the BASH, you are ok :-)