From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from main.gmane.org ([80.91.229.2]:33011 "EHLO ciao.gmane.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750755AbXDHLVy (ORCPT ); Sun, 8 Apr 2007 07:21:54 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HaVSy-0000uh-1N for linux-wireless@vger.kernel.org; Sun, 08 Apr 2007 13:21:52 +0200 Received: from ph.xs4all.nl ([80.126.111.3]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Apr 2007 13:21:52 +0200 Received: from phulshof by ph.xs4all.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Apr 2007 13:21:52 +0200 To: linux-wireless@vger.kernel.org From: Pieter Hulshoff Subject: Re: OpenBSD bcw: Possible GPL license violation issues Date: Sun, 8 Apr 2007 11:21:40 +0000 (UTC) Message-ID: References: <200704041945.21447.mb@bu3sch.de> <200704042139.l34LdX54017048@cvs.openbsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: Theo de Raadt writes: > So next time, talk to the specific people, so you don't come off > as being mean, ok? I'm sorry to say this Theo, but you do realize this code was available in the CVS tree, right? Users, especially companies, that use this tree would very likely be interested in knowing that at some point in time this tree contained infringing code, so they can avoid using that version in their own product without being called on it later. If you think this PR is bad, just imagine a company pointing back at your tree as the source for the copyright infringement within their product. This is about trust: if I am to use your code, then I need to be able to trust that there is no infringing code in it, and that if copyright infringement should occur (accidently) at some point in time, that such is discussed in the open so I can avoid (accidently) using that code in my product. With the definition of derivative work as it is, I would think that a clean room approach should be advocated at all times to prevent mistakes like this from happening. Kind regards, Pieter Hulshoff