public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: Creative Commons as an example of a simple license
Date: Thu, 28 Sep 2006 19:29:54 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAENGOLAB.davids@webmaster.com> (raw)
In-Reply-To: <20060928141327.GC32708@DervishD>


> Or for example, you can give your work for free and
> require that it is not used for commercial uses. You're reserving the
> commercialization right for you.

Actually, you can't do that. Copyright law does not permit restriction of
use unless you can condition it on doing something else.

There is no way to prevent someone who lawfully receives a copy of a work
(who doesn't have to go through any click-through or shrink-wrap agreement)
from using it commercially.

You could say that anyone who modifies it or copies it must refrain from
using it commercially. But that wouldn't stop someone who downloaded it from
a web site or bought it on a CD from doing so.

You would essentially have to say that in order to give someone a copy, you
must obtain their affirmative assent to the usage restrictions or require
that works always be packaged in an installer that required their assent to
the terms.

See http://www.copyright.gov/title17/92chap1.html#106 and notice that it
doesn't say anything about commercial use. If someone isn't trying to do any
of those things, copyright won't stop them.

DS



  reply	other threads:[~2006-09-29  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  6:59 Creative Commons as an example of a simple license Esteban Barahona
2006-09-28  9:22 ` DervishD
2006-09-28 12:07 ` Gene Heskett
2006-09-28 14:13   ` DervishD
2006-09-29  2:29     ` David Schwartz [this message]
2006-09-29  7:55       ` DervishD
2006-09-29  9:16         ` 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=MDEHLPKNGKAHNMBLJOLKAENGOLAB.davids@webmaster.com \
    --to=davids@webmaster.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox