What should I pay attention to when using open-source gnu modules in commercial projects? Recently, I was helping a company get a website. The other party proposed to add a questionnaire module, and the questionnaire form was still very complicated. I have read that the open-source system LimeSurvey can meet the requirements, but it can be changed a little bit in the interface and process. After I add this system to my website, can I modify the link in it? For example, the links connecting to the LimeSurvey official website. Gpl indicates that the entire website will be open-source in the future? What should I pay attention to when using open-source gnu modules in commercial projects?
Recently, I was helping a company get a website. The other party proposed to add a questionnaire module, and the questionnaire form was still very complicated.
I have read that the open-source system LimeSurvey can meet the requirements, but it can be changed a little bit in the interface and process.
After I add this system to my website, can I modify the link in it? For example, the links connecting to the LimeSurvey official website.
Gpl indicates that the entire website will be open-source in the future? Where should I put the source code if it is open source?
------ Solution --------------------
If you or the company does not release or sell the modified code as a product ),
You don't need to put your code somewhere...
The link can also be changed.
------ Solution --------------------
Among the various licenses used by free software, the most important thing is the General Public License (GPL ).
Like other free software licenses, GPL permits the public the freedom to run and copy software, the freedom to distribute and disseminate software, and the freedom to obtain the source code of software, the freedom to improve the software and disseminate the improved version to the community.
GPL also stipulates that as long as the modified text is overall or a part of it comes from a program that complies with GPL, the overall modification text must be circulated according to GPL, not only must the source code of the modified text be made public to the public, but restrictions made by the modifier themselves cannot be attached to the circulation of the modified text. Therefore, a program that follows GPL circulation cannot be merged with a non-free software. This circulation rule expressed by GPL is called copyleft, indicating that it is "opposite" to the copyright concept ".
The main principles of the GPL protocol are as follows:
1. ensure that the software is released in open source code from beginning to end, and protect the development results from being stolen for commercial release. Any software, as long as the source program of third-party software protected by the GPL protocol is used and released to non-developers, the software itself automatically becomes the entity protected and restricted by the GPL. In other words, the source code must be open at this time.
2. GPL is generally a manifestation of the copyright on the left (Copyleft, or translated as "anti-copyright", "copyright to the left", "copyright not owned", and "copyright responsibility. You can remove all copyright information from the original version, as long as you keep it open-source and attach a GPL license to the source code and binary version, so that future generations can clearly learn the authorization information of the software. The essence of GPL is that, as long as the software is fully open-source, users are given free space as much as possible, so that the software can develop faster and better.
3. no matter how the software is released, the source code must be included. For example, to provide download on the Web, you must download the source code on the same page of the binary version (if any. If it is released in the form of a CD, the source file must be attached to the CD.
4. companies or individuals who develop or maintain software that complies with the GPL protocol may charge users a certain amount of service fees. The old saying is that the complete source code of the software must be provided free of charge, and the source code and service must not be bundled or sold in disguised form.
I have summarized the following: Open source + service charge available!
