How not to handle a licensing violation
Posted Apr 12, 2007 7:51 UTC (Thu) by drag
In reply to: How not to handle a licensing violation
Parent article: How not to handle a licensing violation
Well do you suppose that the developer didn't realise that people were downloading code from that CVS server?
I don't think that he was that clueless on how CVS works. The excuse stinks.
It's similar to sticking a program (say.. modified GPL'd gimp plugin) on a public website, telling people that it's your copyright, telling people that it's BSD licensed, and then being confused about weither or not this constitutes 'distribution'.
Sounds like the guy is playing up the old OpenBSD anti-GPL arguements about the licensing being confusing and difficult to understand.
The earlier excuse was that was used was that the guy was working on a replacement for GPL'd code and he used functions and bits of logic from the GPL code to aid in the development of his own code. AS a sort of developer crutch, I guess.
As he progressed he would replace the borrowed logic from the GPL'd code with his own.
He made a mistake by forgetting about replacing this and that code snippet. So through the development proccess these bits of bcm43xx code wound up on the public CVS server.
to post comments)