On 5/20/2013 2:14 PM, Jean Lucas wrote:
Is one able to strip the GPL from a repo? In the case of this repo, would the
driver have to be completely reconstructed/reimplemented in the case the GPL
could not be stripped?
As far as the end result goes, be that engineering a new driver or if one can
strip the GPL from the existing repo, the new driver would/could be BSD
licensed, if that decision were up to me.
What does that mean "strip the GPL from a repo"? As in, "hey, I know you
licensed this driver under the GPL but I don't care I'm gonna relicense
it, in violation of the GPL"?
Philip Guenther <guent...@gmail.com> wrote:
On Mon, May 20, 2013 at 8:49 AM, Jean Lucas <horsef...@lavabit.com> wrote:
On 05/20/2013 09:58 AM, Baurzhan Muftakhidinov wrote:
...
You didn't specify the license
GPLv2. One for all, all for one.GNU General Public License, GPL, LGPL,
copyleft, etc.
You should carefully review
http://www.openbsd.org/policy.html
To quote from it:
------
The GNU Public License and licenses modeled on it impose the
restriction that source code must be distributed or made available for
all works that are derivatives of the GNU copyrighted code.
While this may be a noble strategy in terms of software sharing,
it is a condition that is typically unacceptable for commercial use of
software. As a consequence, software bound by the GPL terms can not be
included in the kernel or "runtime" of OpenBSD, though software
subject to GPL terms may be included as development tools or as part
of the system that are "optional" as long as such use does not result
in OpenBSD as a whole becoming subject to the GPL terms.
------
So, if you decide to license your driver under any version of the GPL,
it will not become an official part of OpenBSD as long as it has that
license.
Philip Guenther
