Seven open source protocols that Java programmers must understand

I found several agreements related to the open-source protocol during the occasional online revolution, so I carefully checked some information and shared it with you, the following lists the seven open source protocols that I personally think Java programmers must understand:

Mozilla Public License

Mpl license, which allows free re-release and free modification, but requires that the modified Code be copyrighted by the software initiator. Such authorization protects the interests of commercial software and requires that such software be modified to contribute copyright to the software without charge. In this way, the copyright of all code around the software is concentrated in the hands of the initiator. However, MPL can be modified for free. The 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 it, modify the source code, or use the modified Code as an open-source or proprietary software for release. When you publish code that uses the BSD Protocol, or perform secondary development of your own product based on the BSD Protocol code, you must meet three requirements:

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

2. If you only release binary class libraries/software, you must include the BSD Protocol in the original code in the Library/software documentation and copyright statement.

3. Open-source author/organization name and original product name cannot be used for marketing.

BSD Code encourages code sharing, but it must respect the copyright of the Code author. BSD is a friendly protocol for business integration because it allows users to modify and re-release code, and also allows users to use or develop commercial software release and sales on BSD code. Many companies prefer the BSD Protocol when selecting open-source products, because they have full control over these third-party code and can modify or develop the code twice when necessary.

Apache licence 2.0

Apache licence is a well-known non-profit open-source Apache protocol. Similar to BSD, this Protocol also encourages code sharing and respect for the copyright of the original author. It also allows code modification and re-release (as an open source or commercial software ). Conditions to be met:

1. A copy of Apache licence is required for the code user.

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

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 shall be included.

4. If the product to be released contains a notice file, Apache licence must be included in the notice file. You can add your own license to notice, but it cannot be expressed as a change to Apache licence.

Apache licence is also a friendly license for commercial applications. Users can also modify the code as needed to meet their needs and release/sell as open-source or commercial products.

GPL

GPL licenses are the most widely used software licenses for Free Software. People can modify one or several copies of a program or any part of the program to form derivative works based on these programs. An explicit note must be attached to the modified file: You modified this file and any modification date. You must allow a third party to use the published or published works, including all or part of this program, or all or part of the work derived from this program, under the terms of this License, and cannot be charged for this authorization.

Lgpl

Linux uses GPL. The GPL protocol and BSD, Apache licence, and other licenses that encourage code reuse are very different. The starting point of GPL is the open-source/free use of code and the open-source/free use of reference/modification/derivative code, however, modification and derivative code generation cannot be released and sold as commercial software with closed source. That's why we can use a variety of free Linux, including commercial companies' Linux and Linux various free software developed by individuals, organizations, and commercial software companies.

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

Because GPL strictly requires that software products that use the GPL class library use the GPL protocol, for open source code that uses the GPL protocol, commercial software or departments that require code confidentiality are not suitable for integration/adoption as the basis for class libraries and secondary development.

Other details, such as the GPL protocol, need to be included in the re-release and similar to BSD/Apache.

Public Domain

Public Domain authorization. Authorize the software to a public domain. These software packages have no authorization protocol and can be freely used by anyone.

Artistic license

This allows the author to maintain control over further development.

Transferred from: itpub