|
|
|
|
|
by cyphar
270 days ago
|
|
The idea that not using the "fork" button on GitHub is somehow obscuring authorship is unhinged -- the actual license only requires you keep license headers intact (if your license headers don't convey authorship properly, you should fix that -- as an aside, this is why I don't like the "Copyright X project and contributors" thing). AFAICS, the fork even has the full commit history of the original project (which isn't even a GPL requirement) so I fail to see how anyone could reasonably see this as obscuring ownership. As someone who has dealt with people maliciously stripping out copyright headers before, this example just smells of someone running out of examples while trying to construct a list of petty grievances. Yes, the README of the fork was updated to stop referencing the original project, what would you expect from a fork? Would it have been nice to add a note that it was forked from another project? Yes (and he did exactly that a month later), but it's really not required and I disagree not doing so it somehow hypocritical. And yes, GitHub forks still have a lot of limitations. I wouldn't use them when creating new projects either. |
|