From: "Jonathan A. George" <jageorge@austin.rr.com>
To: Matthew Jacob <lydianconcepts@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "GPL weasels and the atheros stink"
Date: Sun, 02 Sep 2007 14:05:04 -0500 [thread overview]
Message-ID: <46DB0960.9060405@austin.rr.com> (raw)
In-Reply-To: <7579f7fb0709021131g43768bcet5a0895b5e56540ef@mail.gmail.com>
Matthew Jacob wrote:
> > 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.
>
> I beg to differ. If you want to put things out there for others to use
> but want to avoid having the situation as you describe it, simply
> license the work as such (which would be neither BSD nor GPL)-
> requiring any changes to come back to the original maintainer.
> *Snort*. I seem to recall Unix commercial distributions that made
> claims that bug fixes that you made belonged to them.
... But is it _ethical_ (as opposed to legal) to violate the expressed
intent of the original author ...
IP laws (including copyright) are generally used as an imperfect (and
internationally inconsistent) mechanism to protect intent, but inexact
application of those laws affects enforcement as law ... however,
respect for intent remains the ethical standard by which I (for one)
would prefer to govern my life.
--Jonathan--
next prev parent reply other threads:[~2007-09-02 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 17:46 "GPL weasels and the atheros stink" Jonathan A. George
2007-09-02 18:31 ` Matthew Jacob
2007-09-02 19:05 ` Jonathan A. George [this message]
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=46DB0960.9060405@austin.rr.com \
--to=jageorge@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lydianconcepts@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).