開源軟件 許可證密鑰

It's important to take note that there are no good or bad licenses and that no license is superior to another. Anybody can make an open-source license that suits their extravagant, which is the explanation that there are such huge numbers of out there. This could make picking an open-source license a challenging business, particularly for those of us who are not knowledgeable in the terms and conditions and have never had open-source licenses clarified completely. To assist tight with bringing down the choice and understand everything, the OSI set up a rundown of affirmed licenses, comprising of a little more than 80 open source licenses that are most usually utilized.

重要的是要注意，沒有好的許可證，也沒有不好的許可證，并且沒有一個許可證比另一個許可證優越。 任何人都可以制作出適合自己奢侈的開源許可證，這說明存在大量此類許可證。 這可能會使挑選開放源代碼許可證成為一項具有挑戰性的業務，特別是對于我們這些不了解條款和條件并且從未完全闡明開放源代碼許可證的人。 為了幫助您精簡選擇并了解所有內容，OSI設置了肯定的許可證清單，其中包括80多個最常用的開源許可證。

Of the many open source licenses in the OSI approved list, some rule and are utilized by probably the most well-known open-source projects out there. We've tried to list out all of them clarifying the most commonly utilized open source licenses.

在OSI批準列表中的許多開源許可證中，有一些規則可能是最知名的開源項目所利用的。 我們試圖列出所有這些清單，以闡明最常用的開源許可證。

GNU通用公共許可證(GPL) (GNU General Public License (GPL))

The GNU's General Public License is the most well-known open source license around. Richard Stallman made the GPL shield the GNU software from getting exclusive, and it is a particular execution of his "copyleft" idea.

GNU的通用公共許可證是周圍最著名的開源許可證。 理查德·斯托曼(Richard Stallman)使GPL保護GNU軟件免受排斥，這是他的“ copyleft”想法的一個特殊執行。

GPL is a copyleft permit. This implies any product that is composed dependent on any GPL part should be shared or released as open source. The outcome is that any product that uses any GPL open source component is required to release its full source code and the entirety of the rights to modify and share the whole code.

GPL是版權所有者許可。 這意味著依賴于任何GPL組成的任何產品都應作為開源共享或發布。 結果是，任何使用任何GPL開源組件的產品都必須發布其完整的源代碼以及修改和共享整個代碼的全部權利。

There has consistently been some confusion concerning what comprises a 'work dependent on' another work, which triggers the GPL correspondence commitment. The FSF attempted to add greater lucidity to GPLv3 regarding when the correspondence commitment is activated. The FSF even composed another GPL license, the Affero license, to address a particular confusion alluded to as the "ASP loophole".

關于什么構成“依賴于”另一工作的工作一直存在一些混淆，這觸發了GPL對應承諾。 FSF嘗試為GPLv3增加了有關何時激活通信承諾的明晰度。 FSF甚至還組成了另一個GPL許可證，即Affero許可證，以解決所謂的“ ASP漏洞”的特殊困惑。

Also, the FSF attempted to build the similarity of the GPLv3 with different licenses. To consolidate two codes into a bigger work, both the projects must allow it. If such rights are allowed by both the projects' licenses, they are perfect. By making the GPLv3 progressively good, the FSF extended advancement choices.

同樣，FSF嘗試建立具有不同許可證的GPLv3的相似性。 為了將兩個代碼合并為一個更大的工作，兩個項目都必須允許它。 如果兩個項目的許可證都允許使用這些權利，那么它們就是完美的。 通過逐步提高GPLv3的質量，FSF擴展了進階選擇。

Eclipse公共許可證 (Eclipse Public License)

Created by the Eclipse Foundation, the Eclipse Public License (EPL) is an open-source license. It's developed from the Common Public License (CPL). The Eclipse codebase now accessible under the EPL was in the past licensed under the CPL.

Eclipse Public License(EPL)由Eclipse Foundation創建，是一種開源許可證。 它是根據通用公共許可證(CPL)開發的。 現在可以在EPL下訪問的Eclipse代碼庫過去已在CPL下獲得許可。

The EPL license is a type of copyleft license. On the off chance that you change an EPL'ed segment and disperse it in the source code form as a major aspect of your program, you're required to reveal the altered code under the EPL. On the off chance that you circulate such a program in its object code form, you're required to express that the source code can be made accessible to the beneficiary upon demand. You're likewise required to share the strategy for mentioning the source code.

EPL許可證是一種Copyleft許可證。 如果您不希望更改EPL的段并將其分散在源代碼形式中作為程序的主要方面，則需要在EPL下顯示更改后的代碼。 如果您以目標代碼形式分發這樣的程序，則必須表示，受益人可以根據需要使源代碼可訪問。 同樣，您也需要共享提及源代碼的策略。

The EPL shields the author from potential claims or harms caused if an organization utilized his/her part in a business item. It additionally offers a patent award.

如果組織在業務項目中利用了他/她的部分，EPL可以保護作者免受潛在的索賠或損害。 它還提供了專利獎。

麻省理工學院執照 (MIT License)

MIT is one of the most lenient software licenses. Essentially, you can do anything you desire with source code licensed under the MIT license- just if you include a duplicate of the first MIT license and copyright notice to it. Its effortlessness is the explanation for its high adaption rate among engineers.

MIT是最寬松的軟件許可證之一。 本質上，您可以使用根據MIT許可獲得許可的源代碼執行任何您想做的事情-即使您包含第一個MIT許可的副本和版權聲明。 它不費力地解釋了它在工程師中的高適應率。

翻譯自: https://www.includehelp.com/foss/important-license-in-free-and-open-source-software-1.aspx

開源軟件 許可證密鑰

總結

以上是生活随笔為你收集整理的开源软件 许可证密钥_自由和开源软件-1中的重要许可证的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。