Skip to Content.
Sympa Menu

cc-licenses - Re: [cc-licenses] license politics, license forking [was Re: Commercial Rights Reserved]

cc-licenses AT lists.ibiblio.org

Subject: Development of Creative Commons licenses

List archive

Chronological Thread  
  • From: pcreso AT pcreso.com
  • To: Development of Creative Commons licenses <cc-licenses AT lists.ibiblio.org>
  • Subject: Re: [cc-licenses] license politics, license forking [was Re: Commercial Rights Reserved]
  • Date: Tue, 11 Dec 2012 19:39:09 -0800 (PST)

One other approach is to retain relatively few core CC licences, but offer further options under CCPlus, as in the example(s) here http://wiki.creativecommons.org/CCPlus where an CC-NC licence is bundled with additional permissions enabling commercial use (with requirements/limitations). I think organisations using generally CC do not want to draft another licence, which is what CCPlus requires. If you have to draft your own licence anyway, then why use CC at all?

Offering specific CCPlus licences, under the CC banner, for users to adopt, might be preferable to a proliferation of core CC variants. There is a middle ground between CC-branded & non-CC-branded which may enable CC-branded via CCPlus to be more adaptable to meet various user's needs.



Brent Wood



--- On Wed, 12/12/12, Luis Villa <luis AT tieguy.org> wrote:

From: Luis Villa <luis AT tieguy.org>
Subject: [cc-licenses] license politics, license forking [was Re: Commercial Rights Reserved]
To: "Development of Creative Commons licenses" <cc-licenses AT lists.ibiblio.org>
Date: Wednesday, December 12, 2012, 3:29 PM

On Tue, Dec 11, 2012 at 4:53 PM, Mike Linksvayer <ml AT gondwanaland.com> wrote:
>> On Tue, Dec 11, 2012 at 9:56 AM, Heather Morrison <hgmorris AT sfu.ca> wrote:
>>
>> I would also argue in favour of vagueness in some cases over clarity. Creative Commons is about sharing. The
>> concept of sharing is vague, and not understood the same way by everyone. This is true of all abstract concepts,
>> like love, justice, and peace. Some of our best work happens in the realm of the vague - this is the space for
>> expanding our thinking about some very important matters, such as sharing our work rather than locking it down.
>
> Copyheart-NC: ♡ Copying is an act of love, not money. Please copy,
> adapt and share noncommercially.
>
> Compare with copyheart.org
>
>
> ...
>
>
> Somewhere between 5% and 95% seriousness on each reply above; I can't
> decide toward which end.

Having just had a conversation last night about the need for a
WTF-Zero license to combat permission culture, I'm very sympathetic to
the notion that overly formalizing and ossifying licensing can have
detrimental effects.

But I think Mike's off-the-cuff response is, perhaps inadvertently,
the right one. Licenses/unlicenses like Copyheart are an important way
for us to experiment and challenge our settled expectations of what
free cultural licenses can or should do.

The core CC licenses aren't the place for that, though. They should
(and currently do) reflect settled expectations based on a decade of
CC's experience, and a quarter century of free software experience
before that. This license cycle clearly has been, and should remain,
about tweaking that based on concrete lessons learned, not radical
changes based primarily on hypotheticals.

I'd suggest that de-branded forks of the licenses are the right place
to start for this sort of serious experimentation and
norms-challenging. e.g., I'm semi-serious about the WTF-Zero license
(a for of CC-Zero for people who explicitly want to fight permission
culture); and clearly Heather is serious about a license that is
CC-like but with a different relationship to commercial use. This
appears to be permissible already, according to
https://creativecommons.org/policies. So maybe Heather and I need to
go off, write our (un)licenses, and come back for CC 5 in a decade,
with some actual data and experience ;)

[Disclaimer: I'm on the board of an org whose official policy is that
license proliferation is a bad thing. This is absolutely the correct
position overall, but if we're going to move forward with better
licenses, some experimentation has to occur. So, should anyone reading
this be inspired to experiment and write a license: please make sure,
before you experiment, that your license has an important and clearly
defined functional purpose that is significantly different from other
licenses, with license text that strongly supports that purpose, and
ideally with compatibility with other licenses so that the license can
be retired gracefully. We need experimentation, but it isn't a thing
to be done lightly.]

Luis
_______________________________________________
List info and archives at http://lists.ibiblio.org/mailman/listinfo/cc-licenses
Unsubscribe at http://lists.ibiblio.org/mailman/options/cc-licenses

In consideration of people subscribed to this list to participate
in the CC licenses http://wiki.creativecommons.org/4.0 development
process, please direct unrelated discussions to the cc-community list
http://lists.ibiblio.org/mailman/listinfo/cc-community



Archive powered by MHonArc 2.6.24.

Top of Page