You can't technically revoke it. Should we assume that you're kindly
requesting that people distribute the work under the more permissive
license?
--
David Strauss
| da...@davidstrauss.net
Hmm, that doesn't quite sound like my intent.
My intent is that my copyright work be under the more permissive
license. (FreedomDefined.org argues the NC is less permissive than
pure copyright, and maybe this is exactly why?)
My intent is that the work no longer be under the NC license.
Are you saying (without giving legal advice, natch) that I cannot have
my second intention once having put it under the NC in the first
place?
If that is the case, what does that mean for the idea that we can
obtain all copyright holders' permissions to remove the NC from our
collective work?
- Karsten
--
Karsten Wade -- http://iquaid.org | http://Fairy-TaleFarm.com
http://identi.ca/quaid
http://twitter.com/quaid
gpg key : AD0E0C41
Correct. Once you've put your work under a CC license, it's irrevocable.
Now, it would be silly for someone to choose to use or redistribute your
work under the non-commercial license variant when you've also offered
the unrestricted use one as well (because it'd be dumb to risk one's use
being found "commercial"), but they technically could.
It's important that we not express any licensing change as a
"revocation" because that implies that the licenses are revocable.
> If that is the case, what does that mean for the idea that we can
> obtain all copyright holders' permissions to remove the NC from our
> collective work?
We can't ever "remove" the NC license from the collective work. We can,
with all copyright holders' permission, do this:
* "Distribute" the wiki content under the more permissive
(commercial use-tolerant) license
* Stop distributing the wiki content under the NC license
* Require new contributors to license their new and derivative
work, when posted to our wiki, under the more permissive license
Notably, we're not "removing" or "revoking" any existing license to
existing content.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
Makes sense, thanks for the clarification.
An important question is, do other members of the CLS community want
to see our wiki distributed under a different license and future
contributions be under the more permissive CC BY SA?
I'm not overly keen on taking on the work involved, but I'm also not
keen on another-CLS-event-with-a-jailed-up-wiki.
I would absolutely support the change. The "open source way" is about
confidence in your ability to modify and share. The "non-commercial"
restrictions on some CC license variants are notoriously confusing and
thus create a mild chilling effect. For example, the NC clauses are
generally interpreted to disallow recouping your cost of distribution,
so people with Google Adsense on their site may shy away from reposting
the work. Field-of-use restrictions are always a minefield.
> I'm not overly keen on taking on the work involved, but I'm also not
> keen on another-CLS-event-with-a-jailed-up-wiki.
We could change the overall wiki license to be CC-BY-SA and add a
template to existing pages to note the exception to the overall wiki
license. We could then email everyone requesting that they review their
contributions and remove the exception template on pages where they have
sole authorship or could reach consensus with all contributors.
After a few years, we could review any remaining pages with the NC
template and consider deleting them, rewriting them (hard to do as a
non-derivate work), or making a fresh attempt at approval from the
contributors for a license change.
In an overly simplistic comparison:
* CC-BY-SA ~= GPL
* CC-BY ~= BSD
I think either is reasonable.
I'd like to avoid "another-CLS-event-with-a-jailed-up-wiki" too. What license should we use? CC-BY-SA seems reasonable, but I'm not an expert in these matters.
--
Community Leadership Summit - 17th - 18th July 2010, Portland
http://www.communityleadershipsummit.com
Twitter: @CLSummit Hashtag: #cls10
SA ensures the work can't ever become proprietary without permission from every contributor.
SA ensures the work can't ever become proprietary without permission from every contributor.