Comparison of five open source protocols

There are many open-source protocols, and
Currently, 58 open-source protocols have been approved by the Organization.
Type (http://www.opensource.org/licenses/alphabetical

). Common open-source protocols such as BSD, GPL, lgpl, and MIT
All are OSI.
Approved protocol. If you want to open up your own code, it is best to select these approved Open Source protocols.

Here we will look at the four most commonly used open-source protocols and their applicability for developers who are preparing to open-source or use open-source products/
Manufacturer reference.

BSD

Open source protocol (

Original
BSD license

,


FreeBSD license

,


Original BSD license

)

BSD
Open-source protocol is a protocol that gives users great freedom. Basically, users can"
",
You can freely use it, modify the source code, or use the modified Code as an open-source or proprietary software for release.

However"
"
When you use BSD for release
Protocol code, or use BSD
When you develop your own products based on the protocol code:

1. If the re-release product contains the source code, the source code must contain the BSD in the original code.
   Protocol.
   
   
2. If only the binary class library/
   Software, you need/
   The software documentation and copyright statement contain BSD in the original code
   Protocol.
   
   
3. The author of Open Source Code cannot be used/
   The organization name and the original product name are used for marketing.
   
   

BSD
Code sharing is encouraged, but the author's copyright must be respected. BSD
Because users are allowed to modify and re-release code, they are also allowed to use or
Developing Commercial Software Release and sales on code is a friendly protocol for commercial integration. Many companies prefer BSD when selecting open-source products.
Protocol, because the third-party code can be fully controlled and can be modified or re-developed as necessary.

Apache licence 2.0

(

Apache license,
Version 2.0:

, Apache license, Version 1.1

, Apache license, version
1.0

)

Apache Licence
Apache is a famous non-profit open-source organization.
Protocol used. This protocol and BSD
Similarly, we encourage code sharing and respect for the copyright of the original author, and allow code modification and re-release (as an open source or commercial software ). And BSD.
For example:

1. A copy of Apache is required for the code user.
   Licence
   
   
2. If you have modified the code, it is described in the file to be modified.
   
   
3. In the extended code (Modification and code derived from source code), the Protocol, trademark, patent statement in the original code and other instructions required by the original author must be included.
   
   
4. If the released product contains a notice
   File, then in notice
   The file must contain Apache Licence
   . You can
   Add your own license, but it cannot be expressed as a license to Apache
   Composition Change.
   
   

Apache Licence
It is also a friendly license for commercial applications. Users can also modify the code as needed to meet their needs and release the Code as an open-source or commercial product/
Sales.

GPL

(


GNU General Public License

)

Linux
GPL is used.
. GPL
Protocol and BSD, Apache Licence
And so on. GPL
The starting point is the Open Source/
Free use and reference/
Modify/
Open-source/
Free to use, but cannot be modified and derivative code generation as closed source commercial software release and sales. That's why we can use free Linux
Including Linux
And Linux
On a variety of individuals, organizations, and vendors
Free software developed by software companies.

GPL
The main content of the Protocol is as long as it is used in a software ("
Use"
Refers to the class library reference, the modified Code or derivative code) GPL
Protocol product, the software product must also use GPL
Protocol, which must be both open-source and free.This is the so-called"
Contagious"

. GPL
Protocol products can be used as separate products without any problems and enjoy free advantages.

Because GPL
GPL is strictly required
The software product of the class library must use GPL
Protocol, for the use of GPL
Open-source code of the protocol, commercial software, or departments that have confidentiality requirements on the Code are not suitable for integration/
It serves as the basis for class libraries and secondary development.

Other details such as the need to be accompanied by GPL
Protocol and BSD/Apache
And so on.

Lgpl

(


GNU lesser General Public License

)

Lgpl
Is GPL
Is an open source protocol designed for the use of class libraries. And GPL
Requires any use/
Modify/
Derived GPL
The software of the class library must use GPL
Different protocols. Lgpl
Allow commercial software to be referenced through a class library)
Use lgpl
Class Libraries without the need for open-source commercial software code. This enables the use of lgpl
The open source code of the Protocol can be referenced and published and sold by commercial software as class libraries.

However, if you modify lgpl
Protocol code or derivative, all the modified Code, the additional code involved in the modification part, and the derived code must use lgpl
Protocol. Therefore, lgpl
Open-source code of the Protocol is suitable for being referenced by commercial software as a third-party class library, but it is not suitable for lgpl
Based on the Protocol code, the commercial software is used for secondary development through modification and derivation.

GPL/lgpl
Both protect the intellectual property rights of the original author and prevent people from using open source code to copy and develop similar products.

MIT

(MIT

)

MIT
Yes and BSD
The same wide-range License Agreement,
The author only wants to retain the copyright,
There are no other restrictions.
That is to say,
You must include the original license agreement statement in your release,
Whether it is binary or source code.