1. Origin of open source license agreement
According to the Open Source License Agreement in Baidu Encyclopedia's definition:
Free software/open source software is free, free, open source code, and we are free to download, install and use. At the same time, in order to protect the legal rights of authors and contributors, ensure that these software are not stolen by some commercial institutions or individuals, and affect the development of software, the open source community has developed various open source license agreements.
A diagram to understand the difference between open source license agreements, open source licenses GPL, BSD, MIT, Mozilla, Apache and LGPL
2. Definition of open source license agreement
An open source license is a type of license for computer software and other products that allows source code, blueprints or designs to be used, modified and/or shared under determined terms and conditions. Allow end users and commercial companies to review and modify source code, blueprints, or designs to meet their own customization, curiosity, or troubleshooting needs. Open-source licensed software is mostly available for free, but it doesn't have to be. A license that only allows non-commercial redistributions or modifications of the source code for personal use only is generally not considered an open source license. However, open source licenses may have some restrictions, especially regarding the expression of the source of the software, such as requiring the copyright notice to be retained in the author's name and code, or requiring the redistribution of licensed software only under the same license (as in the Copyleft license). A popular set of open source software licenses are licenses approved by the Open Source Program (OSI) based on their Open Source Definition (OSD).
3. Commonly used open source license agreements
- GPL license
- LGPL License Agreement
- MPL License Agreement
- Apache License Agreement
- BSD License Agreement
- MIT License Agreement
GNU GPL (GNU General Public License):As long as the software contains a product or code that complies with the GPL license, the software must also comply with the GPL license and be open source and free, so this license is not suitable for commercial software. The amount of open source software that follows this protocol is extremely large, and most open source software, including Linux systems, is based on this protocol. The four biggest features of the GPL open source license are as follows.
Freedom of reproduction:Copying the software to anyone's computer is allowed and there is no limit to the number of copies.
Freedom of Communication:Allows software to be disseminated in various forms.
Paid Communication:The software is allowed to be sold in various mediums, but the buyer must be informed in advance that the software is available for free; Therefore, generally speaking, open source software is profitable by providing users with paid services.
Freedom of modification:Developers are allowed to add or remove features from the software, but the software must still be licensed under the GPL license.
BSD (Berkeley Software Distribution) license agreement: The User may use, modify, and republish the Software under this License, and may publish and sell the Software as commercial software, provided that the following three conditions are met.
1: If the republished software contains source code, the source code must continue to comply with the BSD license.
2: If there are only binary programs in the republished software, you need to declare in the relevant documentation or copyright file that the original code follows the BSD license.
3: It is not allowed to use the name of the original software, the name of the author or the name of the organization for marketing.
Apache License Version license agreement: While providing copyright and patent licenses to developers, users are allowed to have the freedom to modify and republish code. This license agreement is applicable to commercial software, and the current popular Hadoop, Apache HTTP Server, MongoDB and other projects are based on this license agreement, and program developers must strictly abide by the following four conditions when developing software that follows this agreement.
1: The software and its derivatives must continue to use the Apache license agreement.
2: If the source code of the program has been modified, it needs to be declared in the documentation.
3: If the software is written based on the source code of others, it is necessary to retain the original code agreement, trademark, patent notice and other content information declared by the original author.
4: If there is a declaration file in the republished software, the Apache license agreement and other license agreements must be marked in this file.
MPL (Mozilla Public License, Mozilla Public License) license agreement: Compared with the GPL license, MPL pays more attention to the balance between the source code requirements and revenue of developers.
MIT (Massachusetts Institute of Technology) license agreement：One of the least restrictive open source licenses available, as long as the developer of the program retains the original author's license information in the modified source code, it is generally used in commercial software.
With a basic understanding of the major open source protocols, the above major protocols can be divided into the following in order of strictness:
GPL > LGPL > MPL > Apache > BSD > MIT
Here's a quick recap from a table:
Resources:The hyperlink login is visible.
|
Posted on 5/21/2019 1:25:06 PM
|
|
|
|
Posted on 5/21/2019 1:35:10 PM
|
