问题
long story short, we're forking a free software. The code is under GNU/GPL license, we've tried to collaborate with the original developer but without success. We're improving the software adding a lot of features and unlikely our code will be merged in the original one.
We want to call the new project with a new name, use the same license of course and change the copyright notice in every file.
I know it should be allowed by the GNU/GPL to modify the code and redistribuite but here some questions:
- Is it OK to change the project name? (I guess yes)
- Is is OK to add our copyright notice and remove the original or we should just add our and leave the original copyright notice?
- We have to leave the reference to the old project in the code? (In the header he asks to make a reference to his project/website in case of fork. I guess it's just a suggestion and we could not do it, right?)
回答1:
Sure. In fact, not changing it at least a little would imply it's the original project, which is a bad idea.
You can't remove copyright notices. Add yours on top.
Why do you want to remove the reference to the old project? It's a suggestion, but removing it would be impolite and potentially misleading. The Open Source/Free Software communities value correct attribution.
回答2:
- Yes
- Add your copyright, and a
Portions (c) [whomever] - Might as well. People are going to know anyway, but unless he made it part of the license I don't think it's enforceable.
I don't know. Do they?
Talk to a lawyer
回答3:
Your forked project is no longer the old project so you would have to change the name.
Your new project is derived project from a GPL license so new licence must be the same or compatible with the GPL.
It seems like the right thing to do.
Clearly or darkly?
来源：https://stackoverflow.com/questions/4475319/how-to-rebrand-copyright-a-forked-project-gnu-gpl