Is it okay to change the package names of a GPLv3 source code? [closed]

Question

This code will be used in a student project, which we'll be releasing as GPLv3. However, we cannot use the code directly since the needs of our project are not the same as the original project. We'll be adding a few classes and also modifying existing classes slightly.

So our classes might be incompatible with any software that uses the original classes. So can we rename the package names to reflect our project name? What's the policy about adding names to the copyright? What is the 'right' way to reuse this code?

Answer 1

The GPL places no legal requirement on you to change package names, or not to change them.

However, you are required to retain all copyright notices, and include the existing GPL license details ... and to release the full source code of your derivitive work under the GPL.

The original licensor could in theory impose extra conditions in addition to the standard GPL. However, this something that you should avoid doing because:

1. it creates extra work for downstream users who need to check that the extra conditions don't create a new legal risk, and

2. it may render the license incompatible with true GPL, creating problems when the code is combined with other (GPL'ed) code.

Having said this, if you intend to distribute your application independently of the original one, it is polite to change it so that it is clear who is responsible for it. In the case of Java code, this includes changing package names and using different Maven artifact groups / ids. (To the extent that this is inconvenient, you should view this as part of the "cost" of repurposing existing GPL'ed code.)

Answer 2

[Insert obligatory disclaimer that I am not a lawyer here.]

There is no requirement in GPLv3 that you maintain any names from the original program. You can change whatever you want.

The only requirements are that your program's copyright notices (both in the source code and any interactive notices, if applicable) include all of the following:

• A copyright notice with your name and the current year.
• An indication that your program includes a modified version of the original program.
• The original program's copyright notice, verbatim.

So the copyright notice in your source distribution might look something like this:

Your Program's Name: This is what it does.
Copyright (C) 2012 Your Name.

This program incorporates a modified version of Other Program.
Copyright (C) 2006 Other Programmer.

This program is free software: [...insert GPL boilerplate here...]