What protocol is used for open source PHP code?

BSD protocol

BSD open source protocol is a protocol that gives users great freedom. Developers are free to use and modify the source code, and can also re-release the modified source code as open source or proprietary software. However, there are several requirements:

1. If the re-released product contains source code, the BSD protocol in the original code must be included in the source code.

2. If only binary class libraries/software are redistributed, the BSD protocol in the original code needs to be included in the documentation and copyright statement of the class library/software.

3. Do not use the name of the author/organization of the open source code and the name of the original product for marketing purposes.

Apache License 2.0 (Apache-2.0)

Apache License is a protocol adopted by Apache, a well-known non-profit open source organization. This agreement is similar to BSD. It also encourages code sharing and the copyright of the final original author, and also allows source code modification and redistribution. However, the following conditions also need to be followed:

1. The user of the code needs to be given an Apache License.

2. If the code is modified, it needs to be stated in the modified file.

3. In the derived code (code modified and derived from source code), the agreement, trademark, patent statement and other instructions specified by the original author need to be included in the original code.

4. If the re-released product contains a Notice file, the Apache License must be included in the Notice file. You can add your own license to the Notice, but it cannot be shown as a change to the Apache License.

GPL

The Linux we are very familiar with adopts the GPL. The GPL agreement is very different from licenses such as BSD and Apache License that encourage code reuse. The starting point of the GPL is the open source/free use of the code and the open source/free use of the reference/modification/derivative code, but the modified and derived code is not allowed to be released and sold as closed source commercial software. This is why we can use all kinds of free Linux, including Linux from commercial companies and various free software on Linux developed by individuals, organizations, and commercial software companies.

Since GPL strictly requires that software products that use GPL class libraries must use the GPL protocol, open source codes that use the GPL protocol, commercial software, or departments that have confidentiality requirements for the code are not suitable for integration/adoptation as class libraries. and the basis for secondary development.

LGPL

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

But if you modify the code or derivatives of the LGPL agreement, all modified code, additional code involving the modified part and derivative code must adopt the LGPL agreement. Therefore, the open source code of the LGPL protocol is very suitable for being referenced by commercial software as a third-party class library, but it is not suitable for commercial software that hopes to use the LGPL protocol code as a basis for secondary development through modification and derivatives.

GPL/LGPL both protect the intellectual property rights of original authors and prevent others from using open source code to copy and develop similar products.

Recommended tutorial: PHP video tutorial

The above is the detailed content of What protocol is used for open source PHP code?. For more information, please follow other related articles on the PHP Chinese website!