Since you can always go public later, I take the private approach first FWIW.
How not to handle a licensing violation
Posted Apr 11, 2007 22:26 UTC (Wed) by man_ls (guest, #15091)
Posted Apr 11, 2007 22:49 UTC (Wed) by k8to (subscriber, #15413)
Posted Apr 11, 2007 23:27 UTC (Wed) by MathFox (guest, #6104)
In any decently ran company including third party code and obfucating its source is a cause for termination. The liabilities of illegally redistributing code for a company are huge.
dealing with copyright infringement
Posted Apr 12, 2007 7:56 UTC (Thu) by man_ls (guest, #15091)
Besides, copyright infringement is only a crime if you sue the infringer. The goal of all this "handling licensing violations" is precisely to bring third parties into compliance without suing.
Posted Apr 12, 2007 8:05 UTC (Thu) by k8to (subscriber, #15413)
Posted Apr 12, 2007 11:46 UTC (Thu) by grouch (guest, #27289)
I have to agree with corbet, madscientist, man_ls, and others who advocate a quiet, private attempt at resolution first. I strongly suspect there would have been no appreciable delay in public notification of the problem, by the BSD developer himself, had he been contacted privately with the details of the problem.
Posted Apr 12, 2007 16:54 UTC (Thu) by k8to (subscriber, #15413)
Posted Apr 12, 2007 17:13 UTC (Thu) by man_ls (guest, #15091)
Private notification can be as quick as public notification, if the receiving party reacts promptly to it. Now, an honest, conscious developer would surely react to the private notification with the same swiftness as if she had the public eye on her. Therefore, believing that a public notification can get a swifter response than a private one is equivalent to thinking that the receiving developer is not honest or conscious; or at least that you do not trust said developer to make the right thing on her own. It is natural to feel insulted by such a thought.
The punishment comes if you really think that the developer has done a bad thing, and it is implied by such loaded words as "falsely labelled", "crime", "duped", etc. Then you have to punish the guilty developer, and since you cannot trust someone who did a bad thing you have to go for a public beating.
If you believe the code misuse is the result of an honest mistake, and that it will be prompty resolved, you ought to be much more inclined to try a private notification first.
Posted Apr 12, 2007 17:23 UTC (Thu) by k8to (subscriber, #15413)
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds