Comment: How can I be qualified as an open source software?

I. "Open Source" in China

Software "The licensing method violates the Open Source spirit.

Recently, it was found that many network community software in China is 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 the license agreement in dedecms: It is prohibited to develop any derived version, modified version or third-party version on the basis of the entire or any part of dedecms for redistribution without official permission.
From discuz License Agreement: disallowed in discuz! Any derived version, modified version, or third-party version used for redistribution.
From the license agreement in ecshop: prohibited in ecshop! Any derived version, modified version, or third-party version used for redistribution.
From the license agreement in hdwiki: It is prohibited to develop any derived version, modify version, or third-party version based on the overall or any part of the interactive wiki for redistribution.
The above rules clearly violate the Open Source spirit. The license agreement certified by OSI: 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 the details of the changes. There are many derived versions based on Redhat, such as centos. The famous open-source software sugarcrm has several better derived versions such as vtigercrm and c3crm.

2. How can we be qualified to be known as open-source software?

These self-built license protocols are not strictly open-source software. Open-source software is not only open to the software source code, but also to comply with that license agreement (OSI ), it also includes open-source documentation (user manual and Development Manual ). So how can we be qualified to be known as open-source software? Eric Steven Raymond explained the following:
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 ensure the re-authorization of the modified binary code, which is consistent with the needs of publishers who require accessibility to the software. This approach allows the software authors to require the modified source code to be re-released by adding patches to the original code, this saves the author's original intent and allows 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 resolve 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.

Iii. Some Comments

1. Establish an open-source community
The establishment of an open-source community includes: Project Overview, software download (source code CVS/SVN), documentation (Wiki), bug submission, FAQ, and interactive platform. More people can participate in the development of open-source software.
2. Software License Agreement
Find an open source license agreement that complies with your 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 Mode
The establishment of the SAAs software service model is also an economic source for the survival of the project. There are many software service models, such as ASP Platform services, project implementation services (installation, testing, training, etc.), customized services, development partners, and OEM services.

Note: I am not liable for any of the above content from the Internet.

Article transferred from: http://news.csdn.net/n/20071219/111869.html