Mozilla public license

mpl license allows free redistribution and free modification, but requires that the copyright of the modified code belongs to the initiator of the software. This kind of authorization protects the interests of commercial software, and it requires that copyright be contributed to the software free of charge based on the modification of this software. In this way, the copyright of all codes surrounding the software is concentrated in the hands of the initiating developer. However, MPL is allowed to be modified and used for free. MPL software does not require links.

BSD open source protocol

BSD open source protocol is a protocol that gives users great freedom. You can freely use and modify the source code, and you can also redistribute the modified code as open source or proprietary software. When you publish the code that uses BSD protocol, or develop your own product on the basis of BSD protocol code, you need to meet three conditions:

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

2. If only the binary class library/software is redistributed, you need to include the BSD protocol in the original code in the document and copyright notice 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.

BSD code encourages code enjoyment, but it needs to respect the copyright of the code author. BSD is a protocol that is friendly to business integration because it allows users to modify and redistribute codes, and also allows users to use or develop commercial software distribution and sales on BSD codes. Many companies and enterprises prefer BSD protocol when choosing open source products, because they can completely control the code of these third parties and can modify or redevelop it when necessary.

Apache license 2.

Apache license is a protocol adopted by Apache, a famous non-profit open source organization. Similar to BSD, this protocol also encourages the code to enjoy and respect the copyright of the original author, and also allows the code to be modified and then released (as open source or commercial software). Conditions to be met:

1. You need to give the user of the code an Apache license

2. If you modify the code, you need to explain it in the modified file.

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

4. If the redistributed product contains a Notice file, Apache Licence is required in the Notice file. You can add your own license in Notice, but it can't be shown as a change to Apache Licence.

Apache license is also a business-friendly license. Users can also modify the code when necessary to meet the needs and publish/sell it as an open source or commercial product.

GPL

GPL license is the most widely used software license for free software. People can modify one or several copies of the program or any part of the program to form derivative works based on these programs. It must be clearly stated in the modified file that you modified this file and the date of any modification. You must allow the works you publish or publish, including all or part of this program, or works derived from all or part of this program, to be used by third parties under this license, and you shall not be charged for this authorization.

LGPL

Linux just adopts GPL. GPL protocol is very different from BSD,ApacheLicence and other licenses that encourage code reuse. The starting point of GPL is the open source/free use of code and the open source/free use of reference/modification/derivative code, but the modified and derivative code is not allowed to be published and sold as closed source commercial software. This is why we can use all kinds of free linux, including linux of commercial companies and all kinds of free software developed by individuals, organizations and commercial software companies on linux.

the main content of the GPL protocol is that as long as a product of the GPL protocol is used in a software ("use" refers to class library reference, modified code or derivative code), the software product must also adopt the GPL protocol, which is both open source and free. This is the so-called "infectivity". The products of GPL protocol can be used as a single product without any problems, and they can also enjoy the advantage of free.

because GPL strictly requires that software products using GPL class library must use GPL protocol, open source code using GPL protocol, commercial software or departments with confidentiality requirements on code are not suitable for integration/adoption as the basis of class library and secondary development.

other details such as GPL protocol and BSD/Apache and other similar

Public Domain

public * * * domain authorization should be accompanied when redistributing. License the software as a public domain. These software packages have no license agreement, and anyone can use it at will.

zlib/libpng

As long as the origin of the software is not misinformed and the original announcement is kept, anyone can use the software for any purpose, including commercial application

Artificial license to keep the author in control of further development.

MIT

MIT is a license agreement as broad as BSD, and the author only wants to keep the copyright without any other restrictions. In other words, you must include a statement of the original license agreement in your distribution, whether you distribute it in binary or source code.