A few open source protocols that a Java programmer needs to understand __java

The task of working today is to write someOpen SourceAgreement related to the contract description, so the Internet search for some information for reference, listed below a few more common open source agreements, if you want to understand other agreements and detailed understanding of these agreements, I personally recommend this site: Http://www.opensource.org/licenses/Mozilla Public License
MPL License allows free republishing and free modification, but requires that the modified code be copyrighted to the originator of the software. This authorization maintains the interest of commercial software, which requires that the software be modified for free contributions to the software. In this way, all the code around the software copyright is focused on the launch of the development of human hands. But MPL is allowed to modify, free use. MPL software is not required for links.
BSD Open Source protocol
The BSD Open source protocol is an agreement that gives users a lot of freedom. Can be used freely, modify the source code, or the modified code as open source or proprietary software to redistribute. When you publish code that uses the BSD protocol, or if you are developing your own product two times based on BSD protocol code, you need to meet three conditions:
1. If the republished product contains source code, then the BSD protocol in the original code must be included in the source code.
2. If you are releasing only binary class libraries/software, you will need to include the BSD protocol in the original code in the library/software documentation and copyright notices.
3. Can not use the source code of the author/agency name and the original product name to do marketing.
BSD code encourages code sharing, but it needs to respect the copyright of the author of the Code. BSD, which allows users to modify and redistribute code, also allows the use or development of commercial software publishing and sales on BSD code, and therefore is a friendly agreement for business integration. Many companies choose the BSD protocol when choosing open source products because they can completely control the code of these third parties and can be modified or developed two times when necessary.
Apache Licence 2.0
Apache Licence is a well-known non-profit open source organization Apache adopted the Protocol. The agreement, like BSD, also encourages code sharing and respect for the authorship of the original author, as well as allowing the code to be modified and republished (as open source or commercial software). Conditions that need to be met:
1. User needs to give the code a copy of Apache Licence
2. If you modify the code, you need to be modified in the file to explain.
3. In the extended code (in the code that is modified and derived from the source code), there is a need to include an agreement in the original code, a trademark, a patent statement, and other instructions that the original author requires.
4. If a notice file is included in the republished product, the Apache Licence is required in the notice file. You can add your own permission to the notice, but you cannot represent changes to the Apache licence.
The Apache licence is also a commercial application friendly license. Users can also modify the code when needed to meet the needs and publish/sell as open source or commercial products.
　　 GPL
GPL licenses are the most widely used software licenses for free software, and people can modify one or more copies of the program or any part of the program to form derivative works based on these programs. There must be a clear indication in the modified file that you have modified this file and the date of any modification. You must let a work that you publish or publish, including all or part of the program, or a work derived in whole or in part of the program, allowing a third party to use it under the license terms and shall not be charged for such authorization.
LGPL
Linux is using the GPL. The GPL protocol and the BSD, Apache licence, and other licenses that encourage code reuse are very different. The GPL's starting point is open source/free use of code and reference/modification/derivation code for open source/free use, but does not allow modified and derived code to be published and marketed as closed source commercial software. That's why we have free software developed by individuals, organizations, and commercial software companies on a variety of free Linux, including commercial companies ' Linux and Linux.
The main content of the GPL agreement is to use a product in a software that uses the GPL ("use" refers to a class library reference, modified code or derivative code), then the SOFTWARE product must also adopt the GPL protocol, both open source and free. This is the so-called "contagious". The GPL-agreed product is used as a separate product without any problems and can also enjoy the advantage of free.
Because the GPL requires the use of GPL-class library software products must use the GPL protocol, for the use of GPL open source code, commercial software or the code has confidentiality requirements of the Department is not suitable for integration/adoption as a class library and two of the basis for development.
Other details such as the GPL will need to be accompanied by bsd/apache and similar
　 Public Domain
PublicDomainAuthorized. The software is licensed as a public domain, and these packages do not have an authorization agreement and can be used freely by anyone.
Artistic License
Keep the author in control of further development