From: "Jonathan A. George" <jageorge@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: "GPL weasels and the atheros stink"
Date: Sun, 02 Sep 2007 12:46:54 -0500 [thread overview]
Message-ID: <46DAF70E.9060800@austin.rr.com> (raw)
While the title of Marc's email might be construed as flame bait, it is
disappointing to see that the generally very valid points he has made
(as both a BSD _and_ _GPL_ developer) are being ignored. To make it
simple try answering these two questions:
----
Question #1: Is it _ethical_ (legality aside) to take someone else's
actively maintained work (for example an OpenBSD driver) and make
changes which can not be shared/used by the original developer/maintainer?
Answer #1: Considering that the whole reason I personally choose the GPL
for some projects is to prevent this sort of one way street behavior
_away_ from the original OSS developers/contributors _my_ answer must
be; No it is not ethical.
----
Question #2: Is it _technically beneficial_ to branch an OSS work (for
example an OpenBSD driver) in such a way as to diminish the ability to
share contributions between projects?
Answer #2: It would be fascinating (and sad) to see an attempt at
justifying a yes response to this question.
Please don't let the rude language or defensiveness bought out by this
particular incident distract from doing the right thing. Just because
you legally can (or might be able to) do something doesn't make it right.
--Jonathan--
P.S. As a secondary concern; it could be legally dubious with some
governments to relicense an existing file from the OpenBSD license
(given that the copyright license must remain intact) -- though patches
could themselves _technically_ be GPL. Creating _new_ GPL files which
work _with_ the existing BSD licensed has no such ambiguity, but please
see questions #1 and #2 above -- is it the _right_ thing to do?
next reply other threads:[~2007-09-02 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 17:46 Jonathan A. George [this message]
2007-09-02 18:31 ` "GPL weasels and the atheros stink" Matthew Jacob
2007-09-02 19:05 ` Jonathan A. George
2007-09-02 19:35 ` Jeff Garzik
2007-09-05 6:05 ` H. Peter Anvin
2007-09-02 18:46 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46DAF70E.9060800@austin.rr.com \
--to=jageorge@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.