The tasks of today to write some of the relevant agreement with the open source protocol description, so some information in the online search for information, listed below a few of the more common open source license:
Mozilla Public License
MPL License, to allow free re-released, free changes, but requires the modified code belongs to the software initiator. The authorization to maintain the interests of commercial software, which requires the software be modified based on free contributions to the copyright to the software. In this way, all the code around the software may have initiated the development rights are concentrated in the hands of people too. But the MPL is to allow changes to be free to use. MPL does not require software on the link.
BSD open source license
BSD open source license is a great freedom to the user agreement. Free to use, modify the source code can also be modified code as open source or proprietary software re-release. When you release the code to use the BSD protocol, or Zeyi BSD code base to do the second agreement to develop their own products, you need to meet three conditions:
1. If the re-release of the product contains the source code in the source code to the original code with a BSD agreement.
2. If the re-release only binary libraries / software, you need to libraries / software documentation and copyright statement is included in the original code in the BSD agreement.
3. Can not use open source code's author / agency name and the name of the original product to do marketing.
BSD code to encourage code sharing, but the need to respect the code of copyright. BSD By allowing users to modify and redistribute the code, but also allows the use or development of commercial software on BSD code release and sale, and therefore very friendly to business integration agreement. Many companies and enterprises in the selection of open source products are preferred when the BSD protocol, because you can have full control of a third party's code, when the Bi Yao can modify or secondary development.
Apache Licence 2.0
Apache Licence is well-known non-profit organizations Apache open-source adoption agreement. Similar to the agreement and BSD also encourages code-sharing and respect for the original author's copyright, also allows code changes, and then released (as open source or commercial software). Conditions be met:
1. Need to code the user a Apache Licence
2. If you modify the code, need to be modified in the file description.
3. The extension of the code (source code modifications and derived code) need to deal with the original code, trademarks, patents, and other statements contained in the original description of this requires.
4. If we release the product contains a Notice document, the document required in the Notice with the Apache Licence. Notice you can add your own license, but not reflected on the Apache Licence constitutes a change.
Apache Licence is also business friendly licensing applications. Users can also modify the code when needed to meet the needs and released as open source or commercial product / sales.
GPL
GPL free software license is the most widely used software license, one can modify your copy or copies of the Program or any part of it, thus forming derivative works based on these programs. Must cause the modified files to carry prominent notices stating that: you changed the files and the date of any change. You have to let you publish or published works, including all or part of this program, or contained all or part of this program Suo derivative works, Yun Xu Ci license third parties under the terms of use and not for the Licensing of charges.
LGPL
Linux is to use the GPL. GPL agreement and BSD, Apache Licence to encourage code reuse such a license are very different. The starting point is the code for GPL open source / free to use and reference / modification / derivative open source code / free to use, but does not allow modifications and derived closed-source code as a commercial software releases and sales. This is why we can use a variety of free linux, including commercial companies on a variety of linux and linux by individuals, organizations, and commercial software developed for free software.
GPL is the main content of the agreement as long as the use of a software ("use" means the class library reference, the revised code, or derivative code) GPL agreement, product, software products must also adopt the GPL agreement, both must also be open source and Free. This is the so-called "infectious." GPL agreement product as a separate product to use without any problems, you can also enjoy free advantage.
As the GPL strictly require the use of a GPL library of software products to use GPL agreement, the agreement for the use of GPL open source, commercial software or confidentiality requirements on the department code is not suitable for integration / use as a library and the secondary development basis.
Other details such as when the need to re-release agreements with GPL and BSD / Apache, and the like
Public Domain
Public domain license. The software license for the public domain, these packages without a license, anyone can freely use it.
Artistic License
To keep further development of the control.
No comments:
Post a Comment