Some guy forked a framework to post it as own, don't be that guy.
1–10 of 11 posts
Re: Some guy forked a framework to post it as own, don't be that guy.
#2And not a single response from him on that thread.
Re: Some guy forked a framework to post it as own, don't be that guy.
#3i can't condone the behavior of flyphp but i can't really condone the behavior in the comments of the pull request either.
maybe 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.
Re: Some guy forked a framework to post it as own, don't be that guy.
#4Who cares. You know what this world needs? More overzealous, knee-jerk internet justice.
Re: Some guy forked a framework to post it as own, don't be that guy.
#5i can't condone the behavior of flyphp but i can't really condone the behavior in the comments of the pull request either. maybe 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.
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.
Re: Some guy forked a framework to post it as own, don't be that guy.
#6i can't condone the behavior of flyphp but i can't really condone the behavior in the comments of the pull request either. maybe 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.
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.
so we agree that "It's just stupidity on his part".
we disagree in that i think a community like github should meet stupidity with education, whereas you seem to prefer an angry mob.
Re: Some guy forked a framework to post it as own, don't be that guy.
#7Would be best to wait for a commend by the author before you start having a spaz attack. Maybe the author just isn't an expert on licensing.
Re: Some guy forked a framework to post it as own, don't be that guy.
#8I 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.
Re: Some guy forked a framework to post it as own, don't be that guy.
#9i can't condone the behavior of flyphp but i can't really condone the behavior in the comments of the pull request either. maybe 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.
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?"
How do you fork and re-license appropriately?
Re: Some guy forked a framework to post it as own, don't be that guy.
#10i can't condone the behavior of flyphp but i can't really condone the behavior in the comments of the pull request either. maybe 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.
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?" How do you fork and re-license appropriately?
someone knows, but not me and probably not anyone commenting on the pull request. xD
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.