| |||||||||||||
How not to handle a licensing violationHow not to handle a licensing violationPosted Apr 11, 2007 22:58 UTC (Wed) by drag (subscriber, #31333)In reply to: How not to handle a licensing violation by cventers Parent article: How not to handle a licensing violation
It's just a matter of decorum and perception. That's all.
There is no question in my mind that going public was required. To much potential for people using OpenBSD code.
The lessons learned are:
1. Talk to the developer first BEFORE (not instead of) going public in future if this problem happens again with OpenBSD folks.
2. Ingore Theo completely.
(Log in to post comments)
|
|||||||||||||