Open source doesn’t just mean access to source code. The distribution terms of open source software must meet the following conditions:

1. Free redistribution

If the software being distributed is composed of programs from different sources, the license shall not restrict Any party or organization (party) sells or gives away open source software as a component of the released software.

The license may not charge royalties or any other fees from this sale. (Reason)

2. Source code

The program must include source code, must be allowed to be distributed in source code form, and must also be allowed to be distributed in compiled form. If a part of the product is not distributed with the source code, then there must be a common way to obtain the source code without paying any more than a reasonable fee---free downloading from the Internet is one way to do it. Source code must be in the best possible form for the programmer to modify it. Deliberately obscuring source code is not allowed. Intermediate results from preprocessor or translator processing are also not allowed. (Reason)

3. Derivative Works

The license must permit modifications and derivatives of the software, and must permit their distribution under the terms of the original software's license. (Reason)

4. Integrity of the author's source code

Only if the license permits the distribution of a "patch file" with the source code (the "patch file" was created at the time The license can only restrict the release of source code in modified form if the purpose is to modify the program. The license must explicitly permit distribution of programs generated from modified source code. A license may require that derived works bear a different name or a different version number to distinguish it from the original software. (Reasons)

5. No discrimination against any individual or group

The license shall not discriminate against any individual or group of persons. (Reason)

6. No discrimination against any fields of endeavor (fields of endeavor)

The license shall not restrict anyone from applying the program to any field. For example, it should not be stipulated that the program cannot be applied in the commercial field or in the field of genetic research. (Reason)

7. Issuance of License

The rights associated with the program must apply to any user of the program, and the user of the program must not be required to use the program in order to use the program. and obtain permission from other licenses. (Reason)

8. The license cannot be specific to a product

The rights associated with a program cannot be determined by whether the program is part of a software product. If the Program is extracted from that distribution and used and distributed in accordance with the terms of the Program's license, then the party or organization obtaining the Program acquires the same rights as a user of the original Program. (Reason)

9. License cannot affect other software

A license shall not impose any restrictions on other software distributed with the software using it. For example, a license cannot insist that other programs released on the same medium are open source software. (reason)

Conformance

(This section is not part of the open source definition)

We believe that this open source definition covers the vast majority of The original and current meaning of the term "open source" as used by the software community. However, the term was widely used and its meaning became imprecise. The OSI Certified mark indicates whether a software release license complies with the OST certification method defined by open source code. The generic term "open source" does not provide such a guarantee, but we still encourage use of the term "open source" to indicate compliance with the "open source definition". For information about the OSI Certified mark and licenses that have passed OSI Certified and comply with the "Open Source Definition", see the OSI Certified Mark and Outline.

Principles of the definition of open source code

The purpose of giving the definition of open source code is to combine what we believe is "open source code" recognized by the software development community. The meaning is written down as a set of specific guidelines---the guidelines ensure that software released under an open source license can be reviewed with the same care as other software, so that the software can be continuously improved and selected, thereby providing the benefits of non-open software Reliability and capabilities that are difficult to provide.

To keep this work going, we must resist people stopping contributing to software development for short-term gain. This means that the terms of the license must prevent people from locking up the source code so that only a few people can read and modify it.

When software developers release their software under a license certified by OSI, they can use the "OSI Certified" mark on the software. This certification mark informs users that the software is licensed under an open source definition. For more information about our certification mark and its outline, see OSI Certified Mark and Outline.

1. Free redistribution

By mandating a license that allows free redistribution, we resist any temptation to give up long-term benefits for the sake of a small short-term sales dollar amount. If we don't, there will be a lot of pressure on collaborators to back off their commitments.

2. Source Code

Since software can only be improved through modification, we require easy-to-understand source code. Since our goal is to make the software easy to improve, we also want the software to be easy to modify.

3. Derivative works

Merely providing readable source code is not enough for careful review and rapid improvement and selection of software. To improve software faster, people need to be able to experiment and re-release modifications.

4. Integrity of the author's source code

Encouraging various improvements to software is a good thing, but users have the right to know who is responsible for the software they use . Software authors and maintainers have the right to know what software they support in order to protect their reputations.

Therefore, an open software license must ensure that the source code is readily available, but may require that the source code be released in the form of the original source code and a set of patch files. In this way, "informal" modifications can be obtained while still being easily distinguishable from the original source code.

5. No discrimination against any individual or group

In order to obtain the maximum benefit from this process, as many individuals and groups as possible should be given equal qualifications to make contributions to open source software. Make a contribution. For this reason we prohibit open source licenses from excluding anyone from the process.

6. No discrimination against fields of endeavor

The main purpose of this clause is to prohibit licenses from containing provisions that make open source software unavailable for commercial use. We need business users to engage with our work without making them feel left out.

7. Release of License

The purpose of this clause is to prohibit indirect means, such as the need to sign a non-disclosure agreement, to prevent the software from being disclosed.

8. The license cannot be specific to one product

This clause is used to prevent other license traps.

9. Licenses cannot affect other software

Publishers of open source software have the right to make choices for their own software.

Yes, the GPL meets this requirement. A library released under the GPL only affects (contaminate) the software it is linked to at runtime, and has nothing to do with the software it is released with.

OSI Certified logo and outline

The open source definition gives the basic nature of open source software. Unfortunately, the term "open source" has been abused, and due to its descriptive nature it cannot be protected as a trademark (which is our first choice).

Because the community needs a reliable way to determine whether a piece of software is truly open source software. OSI has registered a certification mark, OSI Certified, for this purpose. If you see this mark on a piece of software, then the software must have been released under a license that complies with the definition of open source. Otherwise, the publisher is abusing the mark and violating the law.

The OSI Certified mark is used for software rather than licenses: what people need to know is that the packages that make up the software and their licenses are open source. Additionally, an individual license may not be "goods" for which a certification mark is registered by the U.S. Patent and Trademark Office. But software authors must obviously be able to confirm at the appropriate moment that their software is released in accordance with OSI Certified open source without asking us (self-certification). So certification proceeds in two steps:

* OSI provides an open source license table that meets the definition of open software source code. These permits undergo detailed public review and are approved by us. If you have a license that you wish to add to this list, please contact license-approval@opensource.org, which initiates the process of obtaining license approval.

* If you wish to set the OSI Certified mark on your software, you can select an approved license from the list and distribute the software under it, marking the software appropriately.

The above is just a summary. Detailed instructions for applying for a license and applying the OSI Certified mark to your software are given below.

Obtaining license approval

1. Email the license to license-approval@opensource.org. In the email, indicate whether you would like to have the license sent to the license discussion list with your signature or anonymously. (We are willing to consider licenses that do not want to be sent out at all, but since review by the community is an important part of approval, we will have to send the license privately to reviewers: therefore, no comments about being sent to the license Approval of licenses on the license discussion list takes longer and usually involves more communication with you)

2. If we find that your license does not meet the definition of open source, we will work with you to resolve the issue.

3. In the meantime, we'll be keeping an eye on the license forum list and working with you to resolve any questions you have that aren't included.

4． As part of this process, we will also seek external legal advice on licensing issues.

5. Once the license meets the open source definition, and there has been sufficient discussion on the license forum or other reviewers have raised no issues that we consider important, we will notify you that the license has been approved and it has been copied Go to our website and be added to the license list below.

Use the logo

You can use the OSI Certified logo on distributions of these two software. The software is released under and meets the requirements of one of the approved licenses, or the source code for the software has been explicitly made publicly available.

In order to show that your software is released in accordance with OSI Certified, you must add one of the following two to your software in the following manner without any modification.

The full statement is:

This software is OSI Certified Open Source Software.

OSI Certified is a certification mark of the Open Source Initiative.

The shorter version The statement is:

OSI Certified Open Source Software

Each distribution form of your software has its own requirements:

* If the software is in electronic form To publish (rather than in tangible form), you must put the complete statement in a README file or similar file that human users will read first.

* If the software is distributed in physical form, you must complete all of the following feasible tasks:

* If the software is distributed in a printed matter, you must include the complete notice in the printed matter.

* If software is distributed on rewritable media (such as floppy disks), CD-ROMs, tapes, etc., they may physically add a brief statement that can be read by the naked eye without Affecting their function, you must label the media with either a full statement or a brief statement.

* If the software is released as a package, the declarations within it cannot be read. You must place the complete declaration outside the package.

If any of the above terms cannot be used for publishing, please contact us and we will add the location of your choice to this list.

Approved Licenses

The following licenses meet the definition of open source and have been approved for use with OSI Certified open source software. Permits with no approval date given 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 that meet the definition include: libpng license, zlib license, IJG JPEG license and OPL (Open LDAP Public License) license