A friend and I have started a project using code from another project, that is covered licensed under GPL. We have distributed it freely on our website, and under its download button, we've added a direct download link to the modified source code also for free. At the about section of the application, we have credited the guys who built the original code. Does the fact that we have a different project name violate the terms of the GPL? And also, if we include the original GPLv2 notice from the original app does that help us comply with it? If not, please state exactly what we have to do to comply with the GPL. The code we're using is an older version, released under GPLv2, and that project has been discontinued, and moved to a different one, where they're still developing. We haven't used any of their current coding, which is released under GPLv3.
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
The GNU General Public License v2 reads:
That means that when your project is based on GPLv2 software, it also has to be released under GPLv2.
For that reason the GPL is often criticized for being a "viral" license - using GPL code in a project "infects" it with the GPL and prohibits you from releasing it under a different license.
To do so you have to:
You avoid a GPL violation by simply adhering to the GPL license terms. From what you describe (your source is available, license terms are still GPLv2, source acknowledged) you've done enough.
You don't need to include the original GPLv2 notice; your own version is sufficient. However, you do need to acknowledge the copyright of the initial contributors.
Using a new project name is no violation of the GPL. It's in fact the norm for forks of OSS projects, and might be required under trademark law.