The Software Freedom Law Show, Episode 0x16 contains numerous bits of interest to CC geeks and is well worth a listen. The show’s hosts, Karen Sandler and Bradley Kuhn of the Software Freedom Law Center, discuss among other things:
- How the GFDL turned out suboptimally — a key point is that developing good public licenses is very hard, the the GFDL was one of the very first for software documentation or other non-software works.
- The migration of Wikipedia and sister projects from GFDL to CC BY-SA, successfully completed this June.
- The importance of public license stewardship by mission-driven nonprofits — Bradley Kuhn’s writing on stewardship has been noted previously on this blog.
- The license used for the show itself, which is CC BY-ND.
- A promise to talk about the public domain and specifically CC0 in a future episode. Looking forward to it.
One quick addendum to the show, in which the hosts wonder if CC has a public versioning process. The answer is yes — see a a list of CC blog posts over the course of development of our 3.0 licenses. The next, eventual versioning will be even more public and rigorous, just as the GPLv3 had a development process far more in depth than that of any public software license that preceded it.Comments Off
We will present a proposal for dual-licensing all Wikimedia projects currently using the GFDL, by January 15, 2009. It will be published on the foundation-l mailing list. This proposal will be discussed and revised through open community discussion, leading to an open vote among all active Wikimedia contributors (to be defined using similar criteria as the Board elections). If a majority of community members favor migration to CC-BY-SA, it will be implemented.
This follows the enormously important November 3 move by the Free Software Foundation to enable FDL-licensed wikis to migrate to CC BY-SA. For more background and why this is so important for free culture, see our post on the FSF’s move.
FSF president and free software movement founder Richard Stallman has since written an open letter on the matter. Excerpt:
If a wiki site exercises the relicensing option, that entails trusting Creative Commons rather than the Free Software Foundation regarding its future license changes. In theory one might consider this a matter of concern, but I think we can be confident that Creative Commons will follow its stated mission in the maintenance of its licenses. Millions of users trust Creative Commons for this, and I think we can do likewise.
This is a great honor for Creative Commons, and a debt of trust we are compelled to uphold. We hope the Wikimedia community will come to the same conclusion. Regarding maintenance of CC BY-SA licenses, see our Statement of Intent, also cited by the Q&A linked at the top of this post.
For a more general take on license stewardship, please see Bradley Kuhn’s post on The FLOSS License Drafter’s Responsibility to the Community, prompted by Stallman’s letter:
The key quote from his letter that stands out to me is: “our commitment is that our changes to a license will stick to the spirit of that license, and will uphold the purposes for which we wrote it.” This point is fundamental. As FLOSS license drafters, we must always, as RMS says, “abide by the highest ethical standards” to uphold the spirit that spurred the creation of these licenses.
Far from being annoyed, I’m grateful for those who assume the worst of intentions and demand that we justify ourselves. For my part, I try to answer every question I get at conferences and in email about licensing policy as best I can with this point in mind. We in the non-profit licensing sector of the FLOSS world have a duty to the community of FLOSS users and programmers to defend their software freedom. I try to make every decision, on licensing policy (or, indeed, any issue) with that goal in mind. I know that my colleagues here at the SFLC, at the Conservancy, at FSF, and at the many other not-for-profit organizations always do the same, too.
CC does not create software licenses (we recommend existing excellent free software licenses, such as the FSF’s GNU GPL), but these are words to take to heart as closely as possible.Comments Off