[CCD] considering a change to derivative works applicability

[Sterling "Chip" Camden]

I like the BSD approach.  I want people to be able to use code from
chipstips.com in commercial applications.  All I ask is that they don't
claim it as their own work, or resell it on its own (CCD).

-----Original Message-----
From: ccd-bounces at softwareliberationfront.org
[mailto:ccd-bounces at softwareliberationfront.org] On Behalf Of Chad Perrin
Sent: Wednesday, June 27, 2007 1:30 PM
To: CCD CopyWrite Community
Subject: Re: [CCD] considering a change to derivative works applicability

On Thu, Jun 21, 2007 at 07:07:30AM -0600, Chad Perrin wrote:
> In relation to recent musings about the effectiveness of license terms in
> bringing about a change in the way people think about copyright, I have
> been revisiting the matter of license heritability characteristics.
> Under the section labeled "DEFINITIONS" in the current form of the
> license, there is a definition for purposes of the CCD CopyWrite license
> of the term "Derivative Work".  It is used elsewhere in the license, most
> relevantly in the section labeled "DISTRIBUTION".
> 
> I'm currently a bit torn on the matter of whether to aim more toward a
> "viral" sort of inheritance characteristic similar to the GPL's and a
> more flexible form such as that of the BSD license.  Recent consideration
> of the practical effects of such license terms on the market penetration
> of a license, as a means of reaching as many people as possible, has led
> me to lean more toward a BSD-like approach to license heritability.
> 
> In essence, the way the BSD license works in this regard, is simplicity
> itself:
>   1. BSD licensed code will always be BSD licensed code.
>   2. Modifications to BSD licensed code will also be BSD licensed code.
>   3. A larger work need not actually be distributed under the BSD
>   license, even if it includes BSD licensed code in such a manner that
>   separating the parts destroys the usefulness of the non-BSD licensed
>   code.

I'd still like some feedback on this issue.  I know the term "copyfree"
kinda stole the show -- and that's fine: it's another issue that needed
addressing.  Maybe we can bring some attention back to the matter of
heritability characteristics of the CCD CopyWrite license, though.


> 
> I'm also considering coining the term "copyfree" as an alternative to
> "copyright" and "copyleft", which would likely be especially appropriate
> to the CCD License if I swung it more toward the BSD license model of
> inheritance.  Feedback is desired.  Comments and questions are welcome.

Ogre (my "partner in crime", as 'twere, in the Software Liberation Front
and a thus far silent member of this list) sprang for the registration of
the copyfree.org domain name for a period of five years.  The matter of
deciding what to do about it is thus no longer something to concern
myself with -- it's registered and protected.  I've started the process
of changing the language on the CCD CopyWrite website so that it refers
to CCD CopyWrite as a "Copyfree" license, as contrasted with a "Copyleft"
license.  I have yet to define "Copyfree" anywhere public, however.  I'll
try to get to that in the next few days.

As for the use of the copyfree.org domain itself, I still need to figure
out how I'll shuffle domains around to make room for hosting it.  Once
that's set up, I'll make sure I put a few minutes into posting something
relevant there, at least.  Suggestions are welcome -- and thanks to those
who gave feedback on the use of the term "copyfree".

Beaucoup thanks to Ogre, of course.

-- 
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
awj @reddit: "The terms never and always are never always true."

_______________________________________________
CCD mailing list
CCD at softwareliberationfront.org
http://softwareliberationfront.org/mailman/listinfo/ccd_softwareliberationfr
ont.org