This question is about a true fork (with new name, different features, different objectives and not targeting a pull request).
When I am developing a new application based on an other project I usually keep the forking link like the example bellow.
Often, when I stumble on true forks on GitHub, that link is not kept. What is the proper way to operate regarding the GPLv2/GPLv3 rules? and what would be the advantages of keeping that link in this situation?
Note that the original project is referred to in the README, the copyright rule are respected and the new project is under the same license. Also I found some information on this answer and I do know that standard GitHub forks (with the link reference) do keep a sort of strong link to the main project (like master project deletion situation or commits/network analysis on the main project).