Definition on open source code (version 1.7)
Open source does not only mean access to source code. The publishing provision for open source software must meet the following conditions:
Free re-release If the published software is composed of a program of different sources, the license does not restrict any parties or organization (Party) sales or gifts as an open source software that is released. Licenses must not request usage fees or any other fees from this sales. (Reasons) The source code program must include source code, must be released in source code, and must be released in the compiled form. If a part of the product is not released with the source code, you must provide a means of providing any fees outside of the reasonable range to get the source code --- Free download from the network is a way. The source code must be the best form for programmers to modify it. Intentionally, the source code is not allowed. The intermediate result of the pre-processor or translator processing is also not allowed. (Reasons) The derived work license must allow the software and derived software to be modified, and they must allow them to be released in accordance with the terms of the license of the original software. (Reasons) The integrity of the author's source code is only available to the programs when the license is released with the source code (this "patch file" (this "patch file" is to be modified to the program when creating). The release of the source code. The license must explicitly allow the release of the program generated by the modified source code. Licenses can require derived works with different names or different version numbers to distinguish from the original software. (Reasons) Do not discriminate against any individual or group license may not discriminate against any individual or a group consisting of multi-person. (Reasons) Do not discriminate against any application area (the Fields of Endeavor) does not restrict anyone to apply the program to any field. For example, the procedure cannot be specified in the field of business sector or genetic research. (Reasons) The issuance of the issuance of the license must be applied to any user of the program, and the user's user does not need to obtain a license for other licenses in order to use the program. (Reasons) The license cannot be determined by the program as part of the program as part of a software product. If the program is drawn from that publishing, use and release according to the terms of the program's license, then the parties or organizations of the program will obtain the same rights as the user who get the original program. (Reasons) The license cannot affect other software licenses to make any restrictions to other software issued with their software. For example, licenses cannot insist on requesting other programs published on the same media to open source software. (reason)
Conformance
(This section is not a part of the open source definition)
We believe this open source code defines the initial meaning and current meaning of the term "open source code" used by the vast majority of software groups. However, the term is widely used, and its meaning is not accurate. The OSI CERTIFIED flag is whether a software release license obeys an OST authentication method defined by an open source code. The general term "open source code" does not provide this guarantee, but we still encourage this term using "Open Source" to indicate that it meets the "open source definition". For information on the OSI CERTIFIED logo, as well as licenses that have passed OSI Certified, consistent with the "Open Source Definition" license, see OSI Certified flags and outlines.
Open source code definition principle
The purpose of the definition of open source is: Write the meaning of "Open Source" recognized by the software development group as a set of specific guidelines --- This criterion ensures that the open source license is permitted The software issued by the certificate can be evaluated by other software, so that the software can be constantly improving and selection, thereby providing non-open software. Reliability and capabilities. In order to make this work continue to develop, we must resist peoples to contribute to software development for short-term benefits. This means that the terms of the license must prevent people from hiding (LOCK UP) source code, resulting in only few people to read and modify it.
When the developer's developer released their software according to the license certified by OSI, they can use the "OSI Certified" flag in the software. This authentication mark informs the user that the license used by the software meets the open source definition. For more information on our certification logo and its outline, see Osi Certified flags and outlines.
Free re-released privilege is free to release, we boycotted any temptation to give up long-term benefits in order to obtain a small amount of short-term sales. If we don't do this, there will be a lot of pressures forcing the partners to give up the promise. Source code can be improved due to software only by modification, so we demand source code for easy understanding. Because our goal is to make the software easy to improve, we also hope that the software is easy to modify. The derived work only provides the source code that can be read, and it is not enough for the implementation of serious review and selection for software. In order to accelerate the speed of improvement software, people need to be able to re-release the modifications. The integrity of the author's source code encourages various improvements to software, but the user has the right to know who should be responsible for the software they use. Software author and maintainers have the entity to know what they need to support the software to maintain their reputation. Therefore, the open software license must ensure that the source code can be easily obtained, but the source code can be required to be published in the form of the original source code and a set of patch files. In this way, "informal" modifications can be obtained while it can easily distinguish them from the original source code. Do not discriminate against any individual or group in order to obtain the greatest earnings from the process, you should contribute to open source software as much as possible. To this end, we prohibit open source licenses to exclude anyone outside of this process. Do not discriminate against any application area (Fields of Endeavor) The main purpose of this clause is to prohibit the provisions of the license to make open source software that cannot be used commercially. We need business users to participate in our work without letting them feel excluded. The purpose of the license is to ban through non-direct means, such as need to sign non-public agreements, so that software cannot be disclosed. The license cannot be used for a product this Territic for preventing other license traps. Licenses cannot affect other software open source software, the issuer of open source software, has the right to make a choice for their own software. Yes, GPL satisfies this requirement. Pressing the library published by the GPL only affects the software that is connected to it when the library is runtime, is not related to the software released with it. The OSI CERTIFIED flag is given the basic nature of open source software. Unfortunately, the term "open source code" was abused, and because of its descriptiveness, it could not be protected as a trademark (this is our preferred). Since the community needs a reliable way to determine if a software is truly open source software. OSI registers a certification mark for this purpose, OSI Certified. If you see this flag on a software, the software is to be published in accordance with license defined by the open source code, otherwise, the issuer is abusing the flag and violating the law. The OSI CERTIFIED flag is used for software instead of a license: people need to know that the package and their licenses are open source code. In addition, a separate license may not be "goods", which is registered by the US Patent and Trademark Office. However, the author of the software clearly must be able to confirm that their software is released in accordance with OSI Certified open source in the appropriate time without asking us (self-certification). Therefore, the authentication is performed in two steps: * OSI provides an open source license table that meets the open software source code defined. These licenses have been reviewed by the public and they are approved. If you have a license that I want to join the list, please contact License-Approval@opensource.org, which launches programs approved by the license. * If you want to set the OSI CERTIFIED flag on your software, you can select a license for approved licenses from the list and make a logo for software according to it. It is just a summary.
Detailed description of the application approved license and applying the OSI Certified flag on your software. Get a license approval 1. Send the license to license-approval@opensource.org via email. In an email, you are willing to send a license to a license discussion list in your signature or anonymous. (We are willing to consider those licenses that do not want to be sent, but due to an important part of the community's review, we will have to send the license privately to the reviewer: therefore, the pair is not sent to the license Approved by the license in the list of licensions, take longer, and usually communicate more with you.) 2. If we find that your license does not meet the definition of open source, we will solve this problem with you. 3. At the same time, we will pay attention to the list of license forums and work with you to solve any unsended problems raised by everyone. 4. As part of the process, we will also seek legal advice on the license issue to the outside world. 5. Once the license meets the definition of open source, and after a full discussion or other reviewers in the license forum have not raised what we think is important, we will notify you that the license has been approved, and it is copied Go to our website and have been added to the following license list. Using this flag You can use the OSI CERTIFIED flag on both software issuance. The software's release includes and reaches a request for a license in the approved license list, or the source code of the software has been explicitly placed in the position you can get. In order to indicate that your software is published in OSI CERTIFIED, you have to add one of the two below, and add your software as follows. Complete statement is: this Software Is Osi Certified Open Source Software. OSI CERTIFIED Is A Certification Mark of The Open Source Initiative. The shortcoming statement is: OSI CERTIFIED Open Source Software Your software has its own request : * If the software is published in the form of electronics (rather than Tangible), you must put a complete statement in the readme file or similar, and the human user will first read the file. * If the software is released in kind, you have to complete all the following tasks:
