Open-source protocols

Preface

Since Richard Stallman founded Free Software found in 1985, open source has sprung up and has been developing in full swing. Small to a Java or JS component and a Linux operating system. Open-source software has evolved from only open-source software to more features such as innovation, compilation, fast, and elasticity.

Of course, open-source freedom does not mean that there is no limit at all. Different open-source software has different open-source protocols.

Private developers may not be concerned about these protocols. However, for software development companies or individuals who want to commercialize software, if they do not care about this, they are likely to assume some legal responsibilities.

Common open-source protocols and differences

Currently, Common Open Source protocols include:

GPL, lgpl, Apache 2.0, BSD, and MIT.

GPL: Stands for General Public License, which is an informal Chinese Translation of GNU General Public Authorization. It is not published by the Free Software Foundation, nor is it a statutory release term for software using the GNU General Public License

GPL, written by stoman, is used for the GNU program. It is based on earlier versions of GNU Emacs, GDB, and GCC licenses. These licenses all contain some GPL copyright ideas, but only for specific procedures. Stoman's goal is to create a license that can be used within four seas, so as to benefit many source code sharing programs.

The icon of the goat's head is certainly not unfamiliar.

If the software you develop uses an open-source software with the GPL protocol, your software must also be open-source for free and contain your own code.

Lgpl:Lgpl is the abbreviation of GNU lesser General Public License (GNU wide General Public License). It was previously called GNU Library General Public License (GNU Library General Public License) and later called lesser GPL, this is a more loose GPL, which is similar to the BSD, Apache, and xfree86 licenses. GPL (General Public License) and lgpl are two types of GNU license. More and more free software uses GPL as its authorization statement. If you do not know GPL at all, you may violate GPL authorization when using free software, I am afraid there will be a risk of being sued.

Basically,

If the software you develop uses an open-source software with lgpl protocol, your software must be open-source for free. The source code of the original component you modified must be open-source.

Apach 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 ). The conditions to be met are similar to those of BSD:

A copy of Apache licence is required for the code user.
If you have modified the code, you must describe it in the modified file.
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.
If the published product 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.

For example:

If the software you develop uses an open-source software of the apach2.0 protocol, your software must be free of charge. You can choose not to open-source software, but you need to describe the copyright information you use. You do not need to open-source any part of the source code or your own code.

BSD:

BSD is"BerkeleySoftware Distribution "stands for" Berkeley Software release ".

BSD open source protocol is a protocol that gives users great freedom. Basically, users can "do whatever they want", use them freely, modify the source code, or release the modified Code as open source or proprietary software. However, when you publish code using the BSD Protocol or develop 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

For example:

If the software you develop uses a BSD Protocol open source software, your software will be charged, but you may not open source it, but you need to describe the copyright information you use.

MIT:

The name of the MIT license is derived from the Massachusetts Institute of Technology (MIT), also known as the "x license" or "X11 license)

The MIT content is similar to the 3-clause BSD license, but it gives software owners greater rights and fewer restrictions.

This Protocol is relatively loose.

A simple look at the figure:

Open-source protocols