Shulou(Shulou.com)06/03 Report--

This article focuses on "what are the common open source protocols". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn what common open source protocols are.

There are probably hundreds of open source licenses (Open Source License) in the world. Today we will introduce some of our common open source protocols. There are GPL, BSD, MIT, Mozilla, Apache and LGPL and so on.

BSD

BSD is an acronym for "Berkeley Software Distribution", which means "Berkeley software release".

BSD open source protocol: a protocol that gives users a lot of freedom. You can use it freely, modify the source code, or redistribute the modified code as open source or proprietary software. When you release code that uses the BSD protocol, or re-develop your own product based on the BSD code, you need to meet three conditions:

If the re-released product contains the source code, the BSD protocol from the original code must be included in the source code. If only the binary library / software is released, the BSD protocol from the original code needs to be included in the library / software documentation and copyright notice. You cannot use the name of the author / organization of the open source code and the name of the original product for marketing.

BSD code encourages code sharing, and also allows commercial software to be released and sold using or developed on BSD code, so many companies prefer BSD protocol when choosing open source products, because they can completely control these third-party codes and can modify or redevelop them when necessary.

Apache Licence

Apache Licence (Apache license), a free software license issued by the Apache Software Foundation, was originally written for Apache http servers.

The agreement, similar to BSD, also encourages code sharing and the ultimate copyright of the original author, and also allows source code modification and redistribution.

Apache Licence is also a business-friendly license, and users can modify the code as needed to meet the release / sale of open source or commercial products.

However, the following conditions also need to be followed:

You need to give the user of the code a copy of Apache Licence. If you modify the code, you need to explain it in the modified code. Derivative code (modifications and code derived from source code) needs to be included with the agreement, trademark, patent declaration and other instructions specified by the original author. If the re-released product contains a Notice file, you need to have Apache Licence in the Notice file. You can add your own license to Notice, but it cannot be expressed as a change to the composition of Apache Licence.

How to quote Apache Licence 2.0 clause Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License")

You may not use this file except in compliance with the License.

You may obtain a copy of the License at

Http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

Distributed under the License is distributed on an "ASIS" BASIS

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

Limitations under the License. GPL

GPL (GUN General Public License): GUN General Public license Agreement.

"Linux uses GPL"

The GPL protocol is very different from the licenses that encourage code reuse, such as BSD, Apache Licence, etc. The starting point of GPL is the open source / free use of code and the open source / free use of referenced / modified / derived code, but modified and derived code is not allowed to be released and sold as closed source commercial software. This is why we can use a variety of free linux, including commercial companies' linux and linux, all kinds of free software developed by individuals, organizations, and commercial software companies.

LPGL

LGPL is an open source protocol designed by GPL for the use of class libraries. Unlike GPL, any software that uses / modifies / derives the GPL class library must adopt the GPL protocol. LGPL allows commercial software to use LGPL class libraries through class library references (ink) without the need for open source commercial software code. This allows open source code using the LGPL protocol to be referenced, published and sold by commercial software as a class library.

However, if you modify the code or derivation of the LGPL protocol, all modified code, the additional code involving the modification and the derived code must use the LGPL protocol. Therefore, the open source code of LGPL protocol is very suitable to be referenced by commercial software as a third-party class library, but it is not suitable for wanting to be based on LGPL protocol code.

Commercial software is adopted.

GPL/LGPL protects the intellectual property rights of the original authors and prevents people from using open source code to copy and develop similar products.

MIT

MIT is a broad license agreement like BSD, derived from the Massachusetts Institute of Technology (Massachusetts Institute of Technology,MiT), also known as the × 11 agreement. The author only wants to retain the copyright without any other restrictions.

Users only need to include the MIT license agreement declaration in the relevant documents of the released source code and binary executable files, and they are free to use, modify the source code, redistribute as commercial software, and even use the name of an open source organization to promote the product.

The only condition of this agreement is that the modified code or distribution package contains the license information of the original author. Suitable for commercial software. The software projects that use MIT are: jquery, Node.js.

MPL (Mozilla Public License 1.1)

The MPL agreement allows free redistribution and modification, but requires that the copyright of the modified code belongs to the initiator of the software. This license protects the interests of commercial software and requires free copyright contribution to the software based on modifications to the software. In this way, the copyright of all the code around the software is concentrated in the hands of the originating developer. But MPL is allowed to be modified and used for free. The MPL software does not require links.

EPL (Eclipse Public License 1.0)

EPL allows Recipients to freely use, copy, distribute, distribute, display, modify and modify the second commercial release of closed sources.

To use the EPL protocol, you need to follow the following rules:

When a Contributors releases the whole or part of the source code again, it must continue to be released in accordance with the EPL open source protocol, rather than using other protocols. Unless you are authorized by the original "source code" Owner; under the EPL agreement, you can release the source code commercially without any changes. But if you want to release the modified source code, or when you re-release Object code, you must declare that its Source Code is available and inform the acquisition method When you need to mix the source code under EPL as part of it with other private sources to become a Project release, you can release the entire Project/Product as a private protocol, but declare which part of the code is under EPL, and declare that that part of the code continues to follow the EPL; independent module (Separate Module) and does not need to open source. At this point, I believe you have a deeper understanding of "what are the common open source protocols?" you might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.