How can it be called Open Source Software?

It is found that many software in China are open-source. But it's strange that they all have their own software license agreement. These software license agreements conflict with the spirit of open source itself. For example:
From discuz! License Agreement in NT: discuz! The overall or any part of NT is based on any derived version, modified version, or third-party version for redistribution. If there is no conflict with other terms, secondary development or integration for the purpose of self-use is allowed, but it is also subject to the constraints and restrictions of the above 3rd items, that is, the discuz is retained! NT name and link.
The above rules clearly violate the open-source spirit and pass the OSI-certified License Agreement: for example, the gnu gpl, MPL, BSD and other license protocols clearly stipulate the right to modify the version or third-party version for redistribution, but ensure that the system you release must also be open-source, note all the points you have modified. The famous open-source software sugarcrm has several good derived versions, such as vtigercrm and c3crm.
These self-built license protocols are not strictly open-source software. Open-source software is not just software. Source code In addition to this, the open-source documentation (user manual and development manual) should also be included in compliance with the license agreement (OSI-recognized ). So how can we be qualified to be known as open-source software? Eric Steven Raymond provides the following explanation:
Based on the purpose of the license, we can differentiate the various rights granted to you by the license. The right to copy and re-release, the right to use, the right to modify for personal purposes, and the right to publish the modified work. A license may impose restrictions on these rights or provide additional conditions. Opensource.org is the result of various thoughts on software "Open Source" or "free. Restrictions on the site license include:
1. Unrestricted copy permission.
2. Unlimited use right.
3. Unrestricted rights to be modified for personal purposes.
These guidelines guarantee the modified binary Code That is consistent with the needs of publishers who require accessibility to software. This approach allows software authors to require the modified source code to patch the original code. Program In this way, the author's original intention is preserved, while allowing them to "Review" other people's improvements to the project.
OSD (definition of Open Source Code) is a legal definition of the "OSI Open Source Software Certification" certificate. In fact, it is as good as the various definitions of "Free Software" that people have proposed. All standard license agreements (such as MIT, BSD, artistic, GPL, and lgpl protocols) are consistent with this formulation (however, sometimes, such as GPL, there are more restrictions, carefully understand these licenses ).
It is worth noting that some licenses that only allow non-commercial use are not eligible to become open-source licenses, although they advertise themselves as "GPL" or other typical licenses. Such licenses discriminate against special owners or individuals and groups. They impose various restrictions on the re-release practices through the CD channel and other attempts to promote open-source software commercially, so as to make things very complicated.

Nbear, an open-source project of the blog Park, is a good open-source project. nbear adopts the BSD open-source protocol and the project is very successful, it is a model for open-source projects in China. There are several important points worth learning from open-source projects in China:
1. Establish open source Community : The establishment of open-source community content includes: Project Overview, software download (source code CVS \ SVN), documentation (Wiki), bug submission, FAQ, interactive platform. More people can participate in the development of open-source software. Nbear official website (http://nbear.org/) contain these very important content, I hope you support nbear.
2. Software License Agreement: nbear adopts the BSD open source protocol to find an open source license agreement that complies with its own project. Such as GPL, MPL, and MIT. These license agreements can help you deal with organizations and people who violate the rules.
3. Software Service Model: The nbear project also has a link to sponsor | donate nbear, which is also the economic source for the survival of the project. I also saw a piece of announcement in the nbear leader Teddy's knowledge base, "undertaking paid technical consulting and project outsourcing ".