Stripping the license and all author's reference on the work takes effort, no matter how small. It's just stupidity on his part. Thumbs up to the community.
That actually brings an interesting question to mind. As someone who hasn't forked anyone's repository, I am not familiar with the licensing expectations of doing so. Obviously the code you've forked belonged to someone else, but at what point can you say "this is now my creation," or at least, "I own modifications to my fork of this guy's work?"
I wonder if anyone in the pull request thread read the README (which was committed a month or so ago, well prior to the pull request)
Hi, I'm starting this fork of the Laravel framework to fit my needs.
While it was wrong to modify the license file, and we should always observe license fully, this isn't the blatant unattributed theft it's presented as.
I was wondering that too! He has blatantly shown that he has forked Laravel in the README. I kinda feel sorry for the guy, he just doesn't realise you aren't allowed to relicense in the way he did.
10 comments
[ 2.7 ms ] story [ 51.2 ms ] threadmaybe i am too forgiving but i'd attribute this to ignorance before malice.
the pull request was an appropriate response. the berating comments that followed are immature and detract from my sympathy toward the issue.
we disagree in that i think a community like github should meet stupidity with education, whereas you seem to prefer an angry mob.
How do you fork and re-license appropriately?
what if you rewrite the library line for line in another language? do you own it then? what if you rewrite it line for line in the same language?
licensing is not my forte but i'm assuming these are answered questions.
Hi, I'm starting this fork of the Laravel framework to fit my needs.
While it was wrong to modify the license file, and we should always observe license fully, this isn't the blatant unattributed theft it's presented as.