Understanding of Common open-source protocols

When using open source code, you also need to pay attention to the corresponding open source Protocol, especially in commercial applications. The following is a simple summary and understanding of common open source protocols.

 

Assume that the open source code we use is a, and the self-developed source code is B.

 

BSD Protocol

1. If B is open-source and B carries the code of A, B must carry the BSD Protocol DECLARATION OF A at the time of release.

2. If B Closes the source and B carries the code of A, B must carry the BSD Protocol DECLARATION OF A in the document/copyright statement at the time of release.

3. The author of a or any other information cannot be used for marketing of B.

Conclusion: It has a great degree of freedom and is suitable for commercial purposes.

 

Apache protocol:

1. B needs to give the user an Apache license for publishing.

2. If the code of A is modified, it must be specified in the Code file.

3. In B, the agreement, trademark, patent statement, and all content in a that requires the derivative software/class library statement shall be carried.

4. B contains a notice file that contains the Apache license and the content you want to declare. (This content cannot conflict with the Apache protocol itself)

Conclusion: It has a great degree of freedom and is suitable for commercial purposes.

 

GPL protocol:

1. B must comply with the GPL protocol (contagious) and B must be open source and free of charge.

2. B must declare itself as a GPL protocol when publishing.

3. The content of A can be modified in B.

Conclusion: It is not suitable for commercial use and must be open-source and free.

 

Lgpl protocol:

1. If B modifies the content of A, the modified part and additional derivative code must comply with the lgpl protocol.

2. Allow Part B to close the source, link to the derivative part of A or.

Conclusion: It is suitable for commercial use within a certain range.