Author: COSOFT
Definition of open source code
Translator's statement:
This article is an open source code definition, an open source code definition principle, and an OSI CERTIFIED flag and an outline of Chinese translation.
This article was translated by Wang Li in August 1999.
I have made the most efforts to ensure that the translation and the original text consistency in the meaning of the translation, but I can't be pair: any misunderstand caused by the translation and the original text; or misunderstanding of the translation; any direct Indirect losses bear any responsibility.
Wang Li in August 1999
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:
1. Freely release
If the published software is composed of a program of different sources, the license does not limit any open source software that is one of the affiliates or organizations (Party).
Licenses must not request usage fees or any other fees from this sales. (reason)
2. The source code program must include source code, must be released in source code, and must also 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. (reason)
3. Derived work
The license must allow 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. (reason)
4. The integrity of the author's source code is only available when the license is allowed to issue a "patch file" (this "patch file" (this "patch file" to modify the program when creating), the license can limit the source code for modified forms. Release. 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. (reason)
5. Do not discriminate against any individual or group
Licenses may not discriminate against any individual or group consisting of multiplayers. (reason)
6. Do not discriminate against any application area (Fields of Endeavor) Do 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. (reason)
7. The release of the license and the procedure-related rights 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. (reason)
8. Licenses cannot be determined by the procedure for a product and procedure that cannot be determined by 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. (reason)
9. Licenses cannot affect other software licenses to make any restrictions to other software issued with their software. E.g,
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 that this open source code defines the initial meaning and current meaning of the term "open source" used by most 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 Osicertified, in accordance with the "Open Source Definition", see the OSI CERTIFIED flag and the outline. 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 (Lockup) source code, resulting in only a few talents 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.
1. Freely release
Through the enforcement of the permit, we boycotted any temptation to give up long-term benefits in order to obtain a small amount of short-term sales amount. If we don't do this, there will be a lot of pressures forcing the partners to give up the promise.
2. Source code can be improved due to software only by modification, so we have requested the source code that is easy to understand. Because our goal is to make the software easy to improve, we also hope that the software is easy to modify.
3. 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.
4. 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 right 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, "unaptified" modifications can be obtained while it can easily distinguish them from the original source code.
5. 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.
6. 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.
7. The purpose of the license is to ban through non-direct means, such as need to sign non-public agreements, so that the software cannot be disclosed.
8. The license cannot be used for a product this Territic for preventing other license traps.
9. 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. OSI CERTIFIED Sign and Outline
Open source code definition gives 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, Osicertified. 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. But the author of the software clearly must be able to confirm that their software is released in an open source of OSICertified at an appropriate time without asking us. Therefore, certification is performed in two steps:
* OSI provides an open source license table that satisfies 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 an Osicertified flag on your software, you can select an approved license 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 an Osicertified flag application on your software.
Approved by the license
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 Approval of the license in the list of licensions, take longer, and usually exchange more to 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.
Use this sign
You can use the OSI CERTIFIED flag on the issuance of these two software. 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. A 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
Every release form of your software has its own requirements:
* If the software is published in electronic form (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:
If the software's release includes print, you must add a complete statement to the print.
If the software is published on the edible media (such as a soft disk), CD-ROM, tape and other media, they can physically add a short declaration that can be read by the naked eye, without affecting their functions, you must Take a complete statement or a short declaration on the media.
If the publishing of the software is a package, so that the declaration cannot be read. You must place a complete statement outside the package.
If you cannot use any of the above terms to be released, please contact us, we will add your choice to this list.
Get approved license
The following license meets the definition of open source and has been approved for open source software for OSI CERTIFIED. The license did not give the approval date were approved before January 1, 1999.
* The GNU General Public License (GPL);
* The gnu library (lesser) General public license (LGPL);
* The BSD license;
* The x consortium license;
* The artistic license;
* The mozilla public license (MPL);
* The QPL;
Other licenses in line with: libpng license, Zlib license, IJG JPEG license, and OPL (Open LDAP PUBLIC LICENSE) license
