From: Jarek Poplawski <jarkao2@o2.pl>
To: Theodore Tso <tytso@mit.edu>
Cc: Remigiusz Modrzejewski <lkml.only@maxnet.org.pl>,
linux-kernel@vger.kernel.org
Subject: Re: Policy on dual licensing?
Date: Tue, 6 Nov 2007 13:40:18 +0100 [thread overview]
Message-ID: <20071106124018.GA1666@ff.dom.local> (raw)
In-Reply-To: <20071104000443.GB30710@thunk.org>
On 04-11-2007 01:04, Theodore Tso wrote:
> On Sat, Nov 03, 2007 at 12:14:15PM +0000, Remigiusz Modrzejewski wrote:
>> We've all seen the last flame war about Linux stealing BSD code. Due to
>> Theo's bad wording whole discussion rolled around the question about
>> legality of this, a big waste of time (question answered a thousand
>> times). Still, the question about ethics is quite valid...
>
> Please let's not restart the flame war then.
Why not? Is it better to stay enemies forever? Sometimes, after the
war miracles happen and bitter enemies become friends...
...
> [...] There are those who believe that there is nothing wrong,
> either morally, ethically, or legally, with taking BSD code, and not
> dual-licesing it when adding GPL-specific additions. [...]
IMHO, the main problem is talking about these things instead of
some basics:
1. BSD copyright is simple here:
"1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer."
So, when I read on lkml, there are people, thinking they actually
can add here and there something about GPL, or even remove it at
all, we have a problem... Any legal, moral or ethical reasoning
here is useless (but gathering some weapons should be safe bet).
2. After retaining such a copyright, IMHO the war is over and BSD guys
call as the best friends! If we are very clever and stay with this
only, they probably can even become our slaves (if they are so
"incredibly silly" as presumed).
3. Otherwise, we have a problem: anything added or changed looks like
BSD copyrighted too. And this is really a legal, moral and ethical
problem, but it's our internal problem (I doubt BSD people are
silly enough to fight for these additions). If you haven't guessed,
I'm in the earlier camp...
Regards,
Jarek P.
next prev parent reply other threads:[~2007-11-06 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 12:14 Policy on dual licensing? Remigiusz Modrzejewski
2007-11-03 13:37 ` Krzysztof Halasa
2007-11-03 16:36 ` Remigiusz Modrzejewski
2007-11-04 0:04 ` Theodore Tso
2007-11-04 17:30 ` Remigiusz Modrzejewski
2007-11-06 12:40 ` Jarek Poplawski [this message]
2007-11-05 23:13 ` David Schwartz
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=20071106124018.GA1666@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml.only@maxnet.org.pl \
--cc=tytso@mit.edu \
/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