public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <lkml@dervishd.net>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Creative Commons as an example of a simple license
Date: Thu, 28 Sep 2006 16:13:27 +0200	[thread overview]
Message-ID: <20060928141327.GC32708@DervishD> (raw)
In-Reply-To: <200609280807.21329.gene.heskett@verizon.net>

    Hi Gene :)

 * Gene Heskett <gene.heskett@verizon.net> dixit:
> On Thursday 28 September 2006 02:59, Esteban Barahona wrote:
> >apparently I "have lines longer than 80 characters" so I have to post
> > like this: http://www.zensui.org/CC/about_GPLv3.html
> 
> [...] However, I wasn't aware that the Creative Commons License was
> a "pick-a-rule" license, where you could drasticly change the
> effect of the license and still call it the CCL.

    It's not exactly a "pick-a-rule" license. I'll try to explain
(but my explanation can be an utter nonsense, so read the licenses
yourself anyway). Just like GPL is "copyleft" and not a "copyright"
because you *grant* rights instead of taking them up, the CC licenses
may be seen as "some rights reserved" instead of "all rights
reserved". That is, you give something but reserver some rights, for
example, the right of attribution. If you reserve that right, derived
works have to carry your name in addition to the person who modified
your work. 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.

    It's a very interesting license because it's like releasing your
work to public domain, but restricting what you may thing is misuse
of your work. I don't find any CC license appropriate for my
software, but I think it is a very interesting license for art,
books, etc. In fact, I find it much better than, for example, GFDL
for books, manuals and other documentation.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

  reply	other threads:[~2006-09-28 14:13 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 [this message]
2006-09-29  2:29     ` David Schwartz
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=20060928141327.GC32708@DervishD \
    --to=lkml@dervishd.net \
    --cc=gene.heskett@verizon.net \
    --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