<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mike Linksvayer &#187; Wikipedia</title>
	<atom:link href="http://gondwanaland.com/mlog/category/wikipedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://gondwanaland.com/mlog</link>
	<description>My opinions only. I do not represent any organization in this publication.</description>
	<lastBuildDate>Thu, 26 Aug 2010 20:54:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Collaborative-Futures.org</title>
		<link>http://gondwanaland.com/mlog/2010/08/26/collaborative-futures-org/</link>
		<comments>http://gondwanaland.com/mlog/2010/08/26/collaborative-futures-org/#comments</comments>
		<pubDate>Thu, 26 Aug 2010 17:11:37 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=975</guid>
		<description><![CDATA[The 2nd edition of Collaborative Futures is now available, and the book has its own site and mailing list&#8211;there will be future editions, and you can help write them. I did a series of posts (also see one on the Creative Commons blog) on the book sprint that produced the 1st edition. The 1st edition [...]]]></description>
			<content:encoded><![CDATA[<p>The 2<sup>nd</sup> edition of <em><a href="http://collaborative-futures.org">Collaborative Futures</a></em> is now available, and the book has its own site and mailing list&#8211;there will be future editions, and you can help write them.</p>
<p><a href="http://collaborative-futures.org"><img src="http://collaborative-futures.org/img/CF_cover.png" style="border:none; text-align:center"/></a></p>
<p>I did a <a href="http://gondwanaland.com/mlog/2010/01/17/collaborative-futures-0/">series of posts</a> (also see <a href="http://creativecommons.org/weblog/entry/21374">one on the Creative Commons blog</a>) on the book sprint that produced the 1<sup>st</sup> edition. The 1<sup>st</sup> edition a highly successful experiment, but unpolished. The 2<sup>nd</sup> edition benefited from contributions by all of the 1<sup>st</sup> edition&#8217;s main collaborators, successfully incorporated <a href="http://www.mushon.com/2010/06/24/collaborative-futures-june-2010-day-1/">new collaborators</a>, and is far more polished. Also see I think the whole team is justifiably proud of the result. Please check it out and subject to harsh criticism, help with the next edition, or both.</p>
<p>You can also republish verbatim, translated, format-shifted, or modified versions, or incorporate into your own materials (e.g., for a class)&#8211;the book and all related assets are released under the <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike license</a> &#8212; the same as <a href="http://creativecommons.org/weblog/entry/15411">Wikipedia</a>. I don&#8217;t think we took advantage of this by incorporating any content from Wikipedia, but as I&#8217;m writing this it occurs to me that it would be fairly simple to create a supplement for the book mostly or even entirely consisting of a collection of relevant Wikipedia articles &#8212; see <a href="http://pediapress.com/books/">examples</a> of such books created using PediaPress; another approach would be to <a href="http://booki-dev.flossmanuals.net/ticket/244">add a feature to Booki</a> (the software used to create <em>Collaborative Futures</em>) to facilitate importing chapters from Wikipedia.</p>
<p>Here&#8217;s a copy of my testimonial <a href="http://blog.booki.cc/?page_id=197">currently on the Booki site</a>:</p>
<blockquote><p>I was involved in the Collaborative Futures book sprint, the first book written using Booki, and the first FLOSS Manuals project that isn&#8217;t software documentation. I was amazed by the results materially and socially, and even more so by the just completed 2nd edition of Collaborative Futures, which successfully incorporated several new contributors and benefited from new Booki features.</p>
<p>I am inspired by the potential for book sprints and the Booki software to expand the scope of collaborative production in a wide variety of contexts, especially education. Booki is an exciting new innovative platform that is bringing book production online and is an important new form of free culture / free knowledge production. Platforms that expand the categories of works that can be radically improved through free collaboration (beyond software and encyclopedias) are absolutely essential to building a good future. I enthusiastically endorse Booki and encourage all to use and support it.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2010/08/26/collaborative-futures-org/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>FundingXBorders</title>
		<link>http://gondwanaland.com/mlog/2010/06/30/fundingxborders/</link>
		<comments>http://gondwanaland.com/mlog/2010/06/30/fundingxborders/#comments</comments>
		<pubDate>Wed, 30 Jun 2010 15:08:51 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=971</guid>
		<description><![CDATA[Today is the last day of a one month Creative Commons fundraising campaign in which all donations go to funding projects proposed by CC affiliates and other organizations &#8212; projects that address a particular bottleneck to CC adoption or build capacity in the global CC movement (e.g., capacity to raise local funds). Please help. I&#8217;m [...]]]></description>
			<content:encoded><![CDATA[<p>Today is the <a href="http://creativecommons.org/weblog/entry/22638">last day</a> of a one month Creative Commons fundraising campaign in which all donations go to funding projects proposed by CC affiliates and other organizations &#8212; projects that address a particular bottleneck to CC adoption or build capacity in the global CC movement (e.g., <a href="http://wiki.creativecommons.org/Grants/Writing_Successful_Applications_--_Online_Funding_Course">capacity to raise local funds</a>). <b><a href="https://support.creativecommons.org/donate">Please help.</a></b></p>
<p>I&#8217;m currently at the COMMUNIA network&#8217;s 2010 conference, <a href="http://www.communia2010.org/"> University and Cyberspace: Reshaping Knowledge Institutions for the Networked Age</a>, where many project leads of CC affiliates in Europe have gathered. It is very good, and very productive, to spend time with so many long-term and long-distance colleagues.</p>
<p>The end of next week <a href="http://identi.ca/alek">Alek Tarkowski</a>, <a href="http://thornet.wordpress.com/">Michelle Thorne</a> and I will hold a <a href="http://wikimania2010.wikimedia.org/wiki/Submissions/Creative_Commons_global_affiliate_network%E2%80%93origin,_role,_future,_including_collaboration_and_shared_learnings_with_Wikimedia_chapters">session at Wikimania</a> on the CC affiliate network&#8217;s origin, role, future, including collaboration and shared learnings with Wikimedia chapters. One of the things we&#8217;ll discuss is the grants program mentioned at the top of this post &#8212; which was largely inspired by <a href="http://meta.wikimedia.org/wiki/Grants">Wikimedia chapter grants</a> and secondarily by Global Voices&#8217; <a href="http://rising.globalvoicesonline.org/">Rising Voices</a>.</p>
<p>There are many interesting challenges and opportunities in building a transnational network, funding and governance among them. For a high-minded perspective, see <a href="http://www.mpifg.de/pu/mpifg_dp/dp08-8.pdf">Epistemic Communities and Social Movements: Transnational Dynamics in the Case of Creative Commons</a> by Leonhard Dobusch and Sigrid Quack. I also highly recommend their blog, <a href="http://governancexborders.wordpress.com">GovernanceXBorders</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2010/06/30/fundingxborders/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Collaborative Futures 2</title>
		<link>http://gondwanaland.com/mlog/2010/01/20/collaborative-futures-2/</link>
		<comments>http://gondwanaland.com/mlog/2010/01/20/collaborative-futures-2/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 10:47:39 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[Open Services]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=899</guid>
		<description><![CDATA[Day 2 of the Collaborative Futures book sprint saw the writing of a number of chapters and the creation of a much more fleshed out table of contents. I spent too much time interrupted by other work and threading together a chapter (feels more like a long blog post) on &#8220;Other People&#8217;s Computers&#8221; from old [...]]]></description>
			<content:encoded><![CDATA[<p>Day 2 of the <em><a href="http://www.booki.cc/collaborativefutures/">Collaborative Futures</a></em> book sprint saw the writing of a number of chapters and the creation of a much more fleshed out table of contents. I spent too much time interrupted by other work and threading together a chapter (feels more like a long blog post) on &#8220;Other People&#8217;s Computers&#8221; from old sources and the theme of supporting collaboration. The current draft is pasted below because that&#8217;s easier than extracting links to sources.</p>
<p><a href="http://gondwanaland.com/mlog/2010/01/18/collaborative-futures-1/">Another</a> tangential observation about the group: I noted a fair amount of hostility toward Wikipedia, the Wikimedia Foundation, and Mediawiki on the notion that they have effectively sucked the air out of other potential projects and models of collaboration, even other wiki software. Of course I am a huge fan of Wikipedia &#8212; I think its centralization has allowed it to scale in a way not possible otherwise &#8212; it has made the community-centric collaboration pie bigger &#8212; and we are very fortunate that such a dominant service has gotten so much right, at least from a freedom perspective. However, the underlying criticism is not without merit, and I tried to incorporate a productive and very brief version of it into the draft.</p>
<p>Also see <a href="http://www.mushon.com/2010/01/19/collaborative-futures-day2-knock-knock-whos-there/">Mushon Zer-Aviv&#8217;s entertaining post on day 2</a>.</p>
<p><small><br />
<h1>Other People&#8217;s Computers</h1>
<blockquote>
<p>Partly because they&#8217;re location-transparent and web-integrated, browser apps support social interaction more easily than desktop apps.
  </p>
<p><em>Kragen Sitaker, &#8220;What&#8217;s wrong with HTTP&#8221;, <a href="http://lists.canonical.org/pipermail/kragen-tol/2006-November/000841.html">http://lists.canonical.org/pipermail/kragen-tol/2006-November/000841.html</a></em>
  </p>
</blockquote>
<p>Much of what we call collaboration occurs on web sites (more generally, software services), particularly collaboration among many distributed users. Direct support for collaboration, and more broadly for social features, is simply easier in a centralized context. It is possible to imagine a decentralized Wikipedia or Facebook, but building such services with sufficient ease of use, features, and robustness to challenge centralized web sites is a very difficult challenge.
</p>
<p>Why does this matter? The web is great for collaboration, let&#8217;s celebrate that! However, making it relatively easy for people to work together in the specific way offered by a web site owner is a rather impoverished vision of what the web (or more generally, digital networks) could enable, just as merely allowing people to run programs on their computers in the way program authors intended is an impoverished vision of personal computing.
</p>
<p>Free software allows users control their own computing and to help other users by retaining the ability to run, modify, and share software for any purpose. Whether the value of this autonomy is primarily ethical, as often framed by advocates of the term free software, or primarily practical, as often framed by advocates of the term open source, any threat to these freedoms has to be of deep concern to anyone interested in the future of collaboration, both in terms what collaborations are possible and what interests control and benefit from those collaborations.
</p>
<blockquote>
<p>Web sites and special-purpose hardware [...] do not give me the same freedoms general-purpose computers do. If the trend were to continue to the extent the pundits project, more and more of what I do today with my computer will be done by special-purpose things and remote servers.
  </p>
<p>What does freedom of software mean in such an environment? Surely it&#8217;s not wrong to run a Web site without offering my software and databases for download. (Even if it were, it might not be feasible for most people to download them. IBM&#8217;s patent server has a many-terabyte database behind it.)
  </p>
<p>I believe that software &#8212; open-source software, in particular &#8212; has the potential to give individuals significantly more control over their own lives, because it consists of ideas, not people, places, or things. The trend toward special-purpose devices and remote servers could reverse that.
  </p>
<p><em>Kragen Sitaker, &#8220;people, places, things, and ideas &#8220;, <a href="http://lists.canonical.org/pipermail/kragen-tol/1999-January/000322.html">http://lists.canonical.org/pipermail/kragen-tol/1999-January/000322.html</a></em>
  </p>
</blockquote>
<p>What are the prospects and strategies for keeping the benefits of free software in an age of collaboration mediated by software services? One strategy, argued for in &#8220;The equivalent of free software for online services&#8221; by Kragen Sitaker (see <a href="http://lists.canonical.org/pipermail/kragen-tol/2006-July/000818.html">http://lists.canonical.org/pipermail/kragen-tol/2006-July/000818.html</a>), is that centralized services need to be re-implemented as peer-to-peer services that can be run as free software on computers under users&#8217; control. This is an extremely interesting strategy, but a very long term one, for it is hard, being at least both a computer science and a social challenge.
</p>
<p>Abstinence from software services may be a naive and losing strategy in both the short and long term. Instead, we can both work on decentralization as well as attempt to build services that respect user&#8217;s autonomy:
</p>
<blockquote>
<p>Going places I don’t individually control — restaurants, museums, retail stores, public parks — enriches my life immeasurably. A definition of “freedom” where I couldn’t leave my own house because it was the only space I had absolute control over would not feel very free to me at all. At the same time, I think there are some places I just don’t want to go — my freedom and physical well-being wouldn’t be protected or respected there.
  </p>
<p>Similarly, I think that using network services makes my computing life fuller and more satisfying. I can do more things and be a more effective person by spring-boarding off the software on other peoples’ computers than just with my own. I may not control your email server, but I enjoy sending you email, and I think it makes both of our lives better.
  </p>
<p>And I think that just as we can define a level of personal autonomy that we expect in places that belong to other people or groups, we should be able to define a level of autonomy that we can expect when using software on other people’s computers. Can we make working on network services more like visiting a friends’ house than like being locked in a jail?
  </p>
<p>We’ve made a balance between the absolute don’t-use-other-people’s-computers argument and the maybe-it’s-OK-sometimes argument in the <a href="http://autonomo.us/2008/07/franklin-street-statement/">Franklin Street Statement</a>. Time will tell whether we can craft a culture around Free Network Services that is respectful of users’ autonomy, such that we can use other computers with some measure of confidence.
  </p>
<p><em>Evan Prodromou, &#8220;RMS on Cloud Computing: “Stupidity”&#8221;, CC BY-SA, <a href="http://autonomo.us/2008/09/rms-on-cloud-computing-stupidity/">http://autonomo.us/2008/09/rms-on-cloud-computing-stupidity/</a></em>
  </p>
</blockquote>
<p>The Franklin Street Statement on Freedom and Network Services is a beginning group attempt to distill actions users, service providers (the &#8220;other people&#8221; here), and developers should take to retain the benefits of free software in an era of software services:
</p>
<blockquote>
<p>The current generation of <strong>network services</strong> or <strong>Software as a Service</strong> can provide advantages over traditional, locally installed software in ease of deployment, collaboration, and data aggregation. Many users have begun to rely on such services in preference to software provisioned by themselves or their organizations. This move toward centralization has powerful effects on software freedom and user autonomy.
  </p>
<p>On March 16, 2008, a workgroup convened at the Free Software Foundation to discuss issues of freedom for users given the rise of network services. We considered a number of issues, among them what impacts these services have on user freedom, and how implementers of network services can help or harm users. We believe this will be an ongoing conversation, potentially spanning many years. Our hope is that free software and open source communities will embrace and adopt these values when thinking about user freedom and network services. We hope to work with organizations including the FSF to provide moral and technical leadership on this issue.
  </p>
<p><span id="more-6"></span></p>
<p>We consider network services that are <strong>Free Software</strong> and which share <strong>Free Data</strong> as a good starting-point for ensuring users’ freedom. Although we have not yet formally defined what might constitute a ‘Free Service’, we do have suggestions that developers, service providers, and users should consider:
  </p>
<p><strong>Developers</strong> of network service software are encouraged to:
  </p>
<ul>
<li> Use the <a href="http://www.fsf.org/licensing/licenses/agpl-3.0.html">GNU Affero GPL</a>, a license designed specifically for network service software, to ensure that users of services have the ability to examine the source or implement their own service.</li>
<li> Develop freely-licensed alternatives to existing popular but non-Free network services.</li>
<li> Develop software that can replace centralized services and data storage with distributed software and data deployment, giving control back to users.</li>
</ul>
<p> <strong>Service providers</strong> are encouraged to:</p>
<ul>
<li> Choose Free Software for their service.</li>
<li> Release customizations to their software under a Free Software license.</li>
<li> Make data and works of authorship available to their service’s users under legal terms and in formats that enable the users to move and use their data outside of the service. This means:
<ul>
<li> Users should control their private data.</li>
<li> Data available to all users of the service should be available under terms approved for <a class="external text" title="http://freedomdefined.org/Licenses" href="http://freedomdefined.org/Licenses">Free Cultural Works</a> or <a class="external text" title="http://opendefinition.org/licenses" href="http://opendefinition.org/licenses">Open Knowledge</a>.</li>
</ul>
</li>
</ul>
<p> <strong>Users</strong> are encouraged to:</p>
<ul>
<li> Consider carefully whether to use software on someone else’s computer at all. Where it is possible, they should use Free Software equivalents that run on their own computer. Services may have substantial benefits, but they represent a loss of control for users and introduce several problems of freedom.</li>
<li> When deciding whether to use a network service, look for services that follow the guidelines listed above, so that, when necessary, they still have the freedom to modify or replicate the service without losing their own data.</li>
</ul>
<p><em>Franklin Street Statement on Freedom and Network Services, CC BY-SA, <a href="http://autonomo.us/2008/07/franklin-street-statement/">http://autonomo.us/2008/07/franklin-street-statement/</a></em>
  </p>
</blockquote>
<p>As challenging as the Franklin Street Statement appears, additional issues must be addressed for maximum autonomy, including portable identifiers:
</p>
<blockquote>
<p align="left">A Free Software Definition for the next decade should focus on the user’s overall autonomy- their ability not just to use and modify a particular piece of software, but their ability to bring their data and identity with them to new, modified software.
  </p>
<p align="left">Such a definition would need to contain something like the following minimal principles:
  </p>
<ol>
<li>data should be available to the users who created it without legal restrictions or technological difficulty.</li>
<li>any data tied to a particular user should be available to that user without technological difficulty, and available for redistribution under legal terms no more restrictive than the original terms.</li>
<li>source code which can meaningfully manipulate the data provided under 1 and 2 should be freely available.</li>
<li>if the service provider intends to cease providing data in a manner compliant with the first three terms, they should notify the user of this intent and provide a mechanism for users to obtain the data.</li>
<li>a user’s identity should be transparent; that is, where the software exposes a user’s identity to other users, the software should allow forwarding to new or replacement identities hosted by other software.</li>
</ol>
<p><em>Luis Villia, &#8220;Voting With Your Feet and Other Freedoms&#8221;, CC BY-SA, <a href="http://tieguy.org/blog/2007/12/06/voting-with-your-feet-and-other-freedoms/">http://tieguy.org/blog/2007/12/06/voting-with-your-feet-and-other-freedoms/</a> </em>
  </p>
</blockquote>
<p>Fortunately the oldest and at least until recently most ubiqitous network service &#8212; email &#8212; accomodates portable identifiers. (Not to mention that email is the lowest common denominator for much collaboration &#8212; sending attachments back and forth.) Users of a centralized email service like Gmail <em>can</em> retain a great deal of autonomy <em>if</em> they use an email address at a domain they control and merely route delivery to the service &#8212; though of course most users use the centralized provier&#8217;s domain.
</p>
<p>It is worth noting that the more recent and widely used if not ubiquitous instant messaging protocol XMPP as well as the brand new and little used Wave protocol are architected similar to email, though use of non-provider domains seems even less common, and in the case of Wave, Google is currently the only service provider.
</p>
<p>It may be valuable to assess software services from the respect of community autonomy as well as user autonomy. The former may explicitly note&nbsp; requirements for the product of collaboration &#8212; non-private data, roughly &#8212; as well as service governance:</p>
<blockquote><p>In cases were one accepts a centralized web application, should one demand that application be somehow constitutionally open? Some possible criteria:</p>
<ul>
<li>All source code for the running service should be published under an open source license and developer source control available for public viewing.</li>
<li>All private data available for on-demand export in standard formats.</li>
<li>All collaboratively created data available under an open license (e.g., one from Creative Commons), again in standard formats.</li>
<li>In some cases, I am not sure how rare, the final mission of the organization running the service should be to provide the service rather than to make a financial profit, i.e., beholden to users and volunteers, not investors and employees. Maybe. Would I be less sanguine about the long term prospects of Wikipedia if it were for-profit? I don’t know of evidence for or against this feeling.</li>
</ul>
<p><em>Mike Linksvayer, &#8220;Constitutionally open services&#8221;, CC0, <a href="http://gondwanaland.com/mlog/2006/07/06/constitutionally-open-services/">http://gondwanaland.com/mlog/2006/07/06/constitutionally-open-services/</a></em></p>
</blockquote>
<p> Software services are rapidly developing and subject to much hype &#8212; referred to by buzzwords such as cloud computing. However, some of the most potent means of encouraing autonomy may be relatively boring &#8212; for example, making it easier to maintain one&#8217;s own computer and deploy slightly customized software in a secure and foolproof fashion. Any such development helps traditional users of free software as well as makes doing computing on one&#8217;s own computer (which may be a &#8220;personal server&#8221; or virtual machine that one controls) more attractive.
</p>
<p>Perhaps one of the most hopeful trends is relatively widespead deployment by end users of free software web applications like WordPress and MediaWiki. StatusNet, free software for microblogging, is attempting to replicate this adoption success, but also includes technical support for a form of decentralization (remote subscription) and a legal requirement for service providers to release modifications as free software via the AGPL.
</p>
<p>This section barely scratches the surface of the technical and social issues raised by the convergence of so much of our computing, in particular computing that facilitates collaboration, to servers controlled by &#8220;other people&#8221;, in particular a few large service providers. The challenges of creating autonomy-respecting alternatives should not be understated.
</p>
<p>One of those challenges is only indirectly technical: decentralization can make community formation more difficult. To the extent the collaboration we are interested in requires community, this is a challenge. However, easily formed but inauthentic and controlled community also will not produce the kind of collaboration we are interested in.
</p>
<p>We should not limit our imagination to the collaboration faciliated by the likes of Facebook, Flickr, Google Docs, Twitter, or other &#8220;Web 2.0&#8243; services. These are impressive, but then so was AOL two decades ago. We should not accept a future of collaboration mediated by centralized giants now, any more than we should have been, with hindsight, happy to accept information services dominated by AOL and its near peers.&nbsp;
</p>
<p>Wikipedia is both held up as an exemplar of collaboration and is a free-as-in-freedom service: both the code and the content of the service are accessible under free terms. It is also a huge example of community governance in many respects. And it is undeniably a category-exploding success: vastly bigger and useful in many more ways than any previous encyclopedia. Other software and services enabling autonomous collaboration should set their sites no lower &#8212; not to merely replace an old category, but to explode it.
</p>
<p>However, Wikipedia (and its MediaWiki software) are not the end of the story. Merely using MediaWiki for a new project, while appropriate in many cases, is not magic pixie dust for enabling collaboration. Affordances for collaboration need to be built into many different types of software and services. Following Wikipedia&#8217;s lead in autonomy is a good idea, but many experiments should be encouraged in every other respect. One example could be the young and relatively domain-specific collaboration software that this book is being written with, Booki.
</p>
<p>Software services have made &#8220;installation&#8221; of new software as simple as visiting a web page, social features a click, and provide an easy ladder of adoption for mass collaboration. They also threaten autonomy at the individual and community level. While there are daunting challenges, meeting them means achieving &#8220;world domination&#8221; for freedom in the most important means of production &#8212; computer-mediated collaboration &#8212; something the free software movement failed to approach in the era of desktop office software.
</p>
<p></small></p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2010/01/20/collaborative-futures-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>AcaWiki</title>
		<link>http://gondwanaland.com/mlog/2009/10/06/acawiki/</link>
		<comments>http://gondwanaland.com/mlog/2009/10/06/acawiki/#comments</comments>
		<pubDate>Tue, 06 Oct 2009 20:53:40 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Prediction Markets]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=822</guid>
		<description><![CDATA[AcaWiki† officiously launches tomorrow. The goal is to make academic knowledge more accessible through wiki community curated article &#8220;summaries&#8221; &#8212; something like long abstracts aimed at a general audience rather than specialists. This could be seen as an end-run around access and copyright restrictions (the Open Access movement has made tremendous progress though there is [...]]]></description>
			<content:encoded><![CDATA[<p>AcaWiki<sup>†</sup> <a href="http://acawiki.org/AcaWiki:PressRelease-2009-10-07">officiously launches tomorrow</a>. The goal is to make academic knowledge more accessible through wiki community curated article &#8220;summaries&#8221; &#8212; something like long abstracts aimed at a general audience rather than specialists.</p>
<p>This could be seen as an end-run around access and copyright restrictions (the Open Access movement has made <a href="http://en.wikipedia.org/wiki/Open_access_%28publishing%29#Adoption_statistics">tremendous progress</a> though there is still much to be done), but AcaWiki is a very partial solution to that problem &#8212; sometimes an article summary (assuming AcaWiki has one) would be enough, though often a researcher would still need access to the full paper (and the full dataset, but that&#8217;s <a href="http://blog.stodden.net/category/reproducible-research/">another battle</a>).</p>
<p>More interesting to me is the potential for AcaWiki summaries to increase the impact of research by making it more accessible in another way &#8212; comprehensible to non-specialists and approachable by non-speedreaders. I read a fair number of academic papers and many more get left on my reading queue unread. A &#8220;human readable&#8221; distillation of the key points of articles (abstracts typically convey next to nothing or are filled with jargon) would really let me ingest more.</p>
<p>Probably the closest things to AcaWiki summaries are <a href="http://researchblogging.org/">Research Blogging</a> and the idea that <a href="http://en.wikinews.org/wiki/RNA_journal_submits_articles_to_Wikipedia">journal authors should contribute to Wikipedia</a>. While both of these are great, blog posts don&#8217;t obtain the benefits (and costs) of distributed authoring and maintenance and direct contribution of research to Wikipedia has <a href="http://en.wikipedia.org/wiki/Wikipedia:What_Wikipedia_is_not#Wikipedia_is_not_a_publisher_of_original_thought">very limited applicability</a>. So I think AcaWiki can make a big contribution. It could turn out that some granularity other than individual article summary is the sweet spot for <a href="http://brianna.modernthings.org/article/137/community-curated-works-ccw">community curation</a> of academic knowledge &#8212; one could imagine field and sub-field and sub-sub-field surveys organized in <a href="http://en.wikipedia.org/wiki/WikiProject">WikiProject</a><sup>††</sup> fashion as that &#8212; but article summaries are a very concrete place to begin, and more should naturally grow out of the AcaWiki community&#8217;s efforts to figure out the best ways to create and organize article summaries.</p>
<p>I&#8217;ve written a summary of Steven Levitt&#8217;s <a href="http://acawiki.org/Why_are_Gambling_Markets_Organised_So_Differently_from_Financial_Markets%3F">Why are Gambling Markets Organised So Differently from Financial Markets?</a> I&#8217;d be really appreciative of article summaries in the following categories:</p>
<ul>
<li>Any paper on prediction markets, in particular from the <a href="http://gondwanaland.com/mlog/2006/05/22/buckingham-markets/">Journal of Prediction Markets</a>.
</li>
<li>Any paper from <a rel="tag" href="http://en.wikipedia.org/wiki/Rejuvenation_Research">Rejuvenation Research</a>.
</li>
<li>Any paper by <a href="http://scholar.google.com/scholar?q=author%3A%22ta+linksvayer%22">my brother</a>.
</li>
<li>Any paper <em>about</em> Creative Commons.
</li>
</ul>
<p><a href="http://acawiki.org"><img src="http://gondwanaland.com/i/acawiki-447x128.png" border="0" align="center"/></a></p>
<p><small><sup>†</sup>I&#8217;ve been somewhat involved in AcaWiki over the past year &#8212; I&#8217;m on its board and Creative Commons has done some technology consulting on the project, credit to <a href="http://yergler.net">Nathan</a> and bits from <a href="http://www.steren.fr/">Steren</a>, <a href="http://natha.nkinka.de/">Nathan K</a>, <a href="http://redprocess.com/">Alex</a> and <a href="http://madebyparker.com/">Parker</a> &#8212; and note that Neeru Paharia, AcaWiki&#8217;s founder, was one of CC&#8217;s earliest employees. AcaWiki summaries are of course contributed under a CC Attribution license, so you can do anything you want with them so long as you link back to the summary.</p>
<p><sup>††</sup>I urge anyone not already impressed by the contribution of WikiProjects on Wikipedia or generally interested in community curation and quality to check out Martin Walker&#8217;s <a href="http://wikimania2009.wikimedia.org/wiki/Proceedings:209">WikiProjects: Improving Wikipedia by organising and assessing articles</a> presented at Wikimania 2009.</small></p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2009/10/06/acawiki/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Content layer infrastructure</title>
		<link>http://gondwanaland.com/mlog/2009/07/25/content-layer-infrastructure/</link>
		<comments>http://gondwanaland.com/mlog/2009/07/25/content-layer-infrastructure/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 05:15:06 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Music]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Peeves]]></category>
		<category><![CDATA[Public Goods]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=772</guid>
		<description><![CDATA[Last Sunday I appeared (mp4 download) on a tech interview program called Press: Here. It went ok. Most of the questions were softball and somewhat repetitive. Lots more could have been said about any of them, but I think I did a pretty good job of hitting a major point on each and not meandering. [...]]]></description>
			<content:encoded><![CDATA[<p><center><a href="http://www.pressheretv.com/?cat=1&#038;subcat=1&#038;video=188"><img src="http://gondwanaland.com/i/pressheretv-linksvayer.jpg"/></a></center></p>
<p>Last Sunday I <a href="http://creativecommons.org/weblog/entry/15939">appeared</a> (<a href="http://www.pressheretv.com/ufiles/flv/PRESS-HERE-21-B-BLOCKMPEG4.mp4" rel="enclosure">mp4 download</a>) on a tech interview program called <em>Press: Here</em>. It went ok. Most of the questions were softball and somewhat repetitive. Lots more could have been said about any of them, but I think I did a pretty good job of hitting a major point on each and not meandering. However, one thing I said (emphasized below) sounds like pure bs:<br />
<blockquote>this has been done in the open source software world for a couple decades now and <em>now that people are more concerned about <b>the</b> content <b>layer that&#8217;s really part of the infrastructure</b></em> having a way to clear those permissions without the lawyer-to-lawyer conversation happen every single time is necessary</p></blockquote>
<div style="padding: 10px; float: right;" about="http://farm4.static.flickr.com/3073/2971255212_f25c3bcbdc_m.jpg" xmlns:cc="http://creativecommons.org/ns#"><a href="http://www.flickr.com/photos/bobchao/2971255212/"><img src="http://farm4.static.flickr.com/3073/2971255212_f25c3bcbdc_m.jpg" style="border: medium none ;"/></a><br /><small><a href="http://www.flickr.com/photos/bobchao/2971255212/" rel="cc:attributionURL" property="cc:attributionName">BobChao</a> / <a rel="license" href="http://creativecommons.org/licenses/by-sa/2.0/">CC BY-SA</a></small></div>
<p>I could&#8217;ve omitted the bolded words above and retained the respect of any viewer with a brain. What the heck did I mean? I was referring to an argument, primarily made by Joi Ito over the last year or so, using a stylized version of the <a href="http://en.wikipedia.org/wiki/Internet_Protocol_Suite#Layers_in_the_Internet_Protocol_Suite">layers of a protocol stack</a>. David Weinberger&#8217;s <a href="http://www.hyperorg.com/blogger/2008/10/08/innovation-and-the-open-internet-joi-ito/">live-blogging of Ito</a> provides a good summary:</p>
<blockquote><p>Way back when, it was difficult to connect computers. Then we got Ethernet, then TCP/IP, and then HTTP (the Web). These new layers allow participation without permission. The cost of sending information and the cost of innovation have gone down (because the cost of failure has gone down). Now we’re getting another layer: Creative Commons. “By standardizing and simplifying the legal layer … I think we will lower the costs and create another explosion of innovation.”</p></blockquote>
<p>Protocol geeks may object, but I think it&#8217;s a fairly compelling argument, at least for explaining why what Creative Commons does is &#8220;big&#8221;. The problems of not having a top layer (I called it &#8220;content&#8221;, the slide photographed above says &#8220;knowledge&#8221; &#8212; what it calls &#8220;content&#8221; is usually called &#8220;application&#8221;, and the note above says &#8220;legal&#8221;, referring to one required mechanism for opening up permissions around content, knowledge, or whatever one wishs to call it) in which a commons can be taken for granted (ie like infrastructure) is evident, for example in the failure by lawsuit of most interesting online music services, or the inaccessibility of much of the scientific literature to most humans and machines (eg for data mining), as are powerful hints as to what is possible where it exists, for example the vast ecology enabled by Wikipedia&#8217;s openness such as <a href="http://gondwanaland.com/mlog/2007/01/23/dbpedia/">DBpedia</a>.</p>
<p>I didn&#8217;t make that argument on-screen. Probably a good thing, given the previous paragraph&#8217;s tortured language. I shall practice. Critique welcome.</p>
<p>&#8230;</p>
<p><em>Press: Here</em> is broadcast from its SF bay area home station (NBC) and I&#8217;ve heard is syndicated to many other stations.  However, its <a href="http://www.pressheretv.com">website</a> says nothing about how to view the program on TV, even on its home station. I even had a hard time finding any TV schedule on the <a href="http://www.nbcbayarea.com/">NBC Bay Area</a> website &#8212; a tiny link in the footer takes one to subpages for the station with lame schedule information syndicated from TV Guide. I found this near total disconnect between TV and the web a very odd, but then again, I don&#8217;t really care where the weird segment of the population that watches TV obtains schedule information. <em>Press: Here</em> ought to release its programs under a liberal CC license as soon as the show airs. Its own website <a href="http://siteanalytics.compete.com/pressheretv.com/">gets very little traffic</a>, many of the interviews would be relevant for uploading to <a href="http://commons.wikimedia.org">Wikimedia Commons</a>, and the ones that got used in Wikipedia would drive significant traffic back to the program website.</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2009/07/25/content-layer-infrastructure/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Conjectured impact of Wikipedia license interoperability?</title>
		<link>http://gondwanaland.com/mlog/2009/05/31/wikipedia-migration-impact/</link>
		<comments>http://gondwanaland.com/mlog/2009/05/31/wikipedia-migration-impact/#comments</comments>
		<pubDate>Sun, 31 May 2009 21:45:11 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Economics]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Prediction Markets]]></category>
		<category><![CDATA[Public Goods]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=739</guid>
		<description><![CDATA[Wikipedians voted overwhelmingly against kryptonite &#8212; for using Creative Commons Attribution-ShareAlike (CC BY-SA) as the main content license for Wikipedias and their sibling projects, permitting these to incorporate work offered under CC BY-SA, the main non-software copyleft license used outside of Wikipedia, and other CC BY-SA licensed projects to incorporate content from Wikipedia. The addition [...]]]></description>
			<content:encoded><![CDATA[<div style="text-align:center"><a href="http://en.wikipedia.org/wiki/File:800px-Cygnus_X-1.jpg"><img src="http://gondwanaland.com/i/Cygnus_X-1-480x300.jpg" title="ESA/Hubble illustration: Cygnus X-1"/></a></div>
<p><a href="http://creativecommons.org/weblog/entry/14668">Wikipedians voted overwhelmingly</a> against <a href="http://gondwanaland.com/mlog/2009/04/13/wikipedians-against-kryptonite/">kryptonite</a> &#8212; for using Creative Commons Attribution-ShareAlike (CC BY-SA) as the main content license for Wikipedias and their sibling projects, permitting these to incorporate work offered under CC BY-SA, the main non-software copyleft license used outside of Wikipedia, and other CC BY-SA licensed projects to incorporate content from Wikipedia. The addition of CC BY-SA to Wikimedia sites should happen <a href="http://meta.wikimedia.org/wiki/Licensing_update/Timeline">in late June</a> and there is an <a href="http://creativecommons.org/weblog/entry/14769">outreach effort</a> to encourage non-Wikimedia wikis under the Free Documentation License (FDL; usually chosen for Wikipedia compatibility) to also migrate to CC BY-SA by August 1.</p>
<p>This change clearly ought to over time increase the proportion of content licensed under <a href="http://creativecommons.org/weblog/entry/8051">free-as-in-freedom</a> copyleft licenses. More content licensed under a single or interoperable copyleft licenses increases the reasons to <a href="http://www.gnu.org/philosophy/pragmatic.html">cooperate</a> with that regime &#8212; to offer new work under the dominant copyleft license (in the non-software case, now unambiguously CC BY-SA) in order to have access to content under that regime &#8212; and decreases the reasons to avoid copylefted work, one of which is the impossibility of incorporating works under multiple and incompatible copyleft licenses (when relying on the permissions of those licenses, modulo fair use). Put another way, the unified mass and thus gravitational pull of the copylefted content body is about to increase substantially.</p>
<p>Sounds good &#8212; but what can we expect from the actual impact of making legally interoperable the mass of Free Culture and its exemplar, Wikipedia? How can we gauge that impact, short of access to a universe where Wikipedians reject CC BY-SA? A few ideas:</p>
<p>(1) Wikimedia projects will be dual licensed after the addition of CC BY-SA &#8212; content will continue to be available under the FDL, until CC BY-SA content is mixed in, at which point the article or other work in question is only available under CC BY-SA. One measure of the licensing change&#8217;s direct impact on Wikimedia projects would be the number and proportion of CC BY-SA-only articles over time, assuming an effort to keep track.</p>
<p>I suspect it will take a long time (years?) for a non-negligible proportion of Wikipedia articles to be CC BY-SA-only, i.e., to have directly incorporated external CC BY-SA content. However, although most direct, this is probably the least significant impact of the change, and my suspicion could be upset if other impacts (below) turn out to be large, creating lots of CC BY-SA content useful for incorporating into Wikipedia articles.</p>
<p>(2) Content from Wikipedias and other Wikimedia projects could be incorporated in non-Wikimedia projects more. The difficulty here is measurement, but given academic interest in Wikipedia and the web generally, it wouldn&#8217;t be surprising to see the requisite data sets (historical and ongoing) and expertise brought together to analyze the use of Wikimedia project content elsewhere over time. Note that a larger than expected (there&#8217;s the rub) increase in such use could be the result of CC BY-SA being more straightforward for users than the FDL (indeed, a major reason for the change) as much or more than the result of license interoperability.</p>
<p>(3) New and existing projects could adopt or switch to CC BY-SA when they otherwise wouldn&#8217;t have in order to gain compatibility with Wikimedia projects. One sure indication of this would involve major projects using a CC license with a &#8220;noncommercial&#8221; term switching to CC BY-SA and giving interoperability with Wikipedia as the reason for the switch. Another indicator would simply be an increase in the use of CC BY-SA (and even more permissive instruments such as CC BY and CC0, to the extent the motivation is primarily to create content that can be used in Wikipedia rather than to use content from Wikipedia) relative to more restrictive (and non-interoperable with Wikipedia) licenses.</p>
<p>(4) Apart from needing to be compatible with Wikipedia because one desires to incorporate its content, one might want to be compatible with Wikipedia because it is &#8220;cool&#8221; to be so. I don&#8217;t know that this has occurred on a significant scale to this date, so if it begins to one possible factor in such a development would be the change to CC BY-SA. How could this be? As cool as Wikipedia compatibility sounds, having to adopt a hard to understand license intended for software documentation (the FDL) makes attaining this coolness seem infeasible. Consideration of the FDL just hasn&#8217;t been on the radar of many outside of the spaces of documentation, encyclopedias, and perhaps educational materials, while consideration and oftentimes use of CC licenses is active in many segments. However, in most of these more restrictive CC licenses (i.e., those prohibiting commercial use or adaptation) are most popular. So if we see an upsurge in the use of CC BY-SA for popular culture works (music, film) the beginning of which coincides with the Wikimedia licensing change, it may not be unreasonable to guess that the latter caused the former.</p>
<p>(5) The weight of Wikipedia and relative accessibility of CC BY-SA could further consensus that the freedoms demanded by Wikimedia projects are some combination of &#8220;good&#8221;, &#8220;correct&#8221;, &#8220;moral&#8221;, and &#8220;necessary&#8221; &#8212; if some of these can be distinguished from &#8220;cool&#8221;. In the long term, this could be indicated by the sidelining of terms for content that do not qualify as <a href="http://freedomdefined.org">free</a> and <a href="http://opendefinition.org/1.0">open</a>, as they have been for software, where <a rel="tag" href="http://en.wikipedia.org/wiki/Shareware">shareware</a> and similar obvious competitors for important free software niches are strategically irrelevant.</p>
<p>Obviously 3, 4, and 5 overlap somewhat.</p>
<p>(6) I <a href="http://www.slideshare.net/mlinksva/how-far-behind-free-software-is-free-culture-presentation">conjecture</a> that making more cultural production more wiki-like (or to gain <a href="http://gondwanaland.com/mlog/2007/03/10/wiki-commercial/">WikiNature</a>) is probably the biggest determinant of the success of Free Culture. More interplay between the Wikipedia, both the most significant free culture project and the most significant wiki, and the rest of the free culture and open content universe can only further this trend &#8212; though I have no idea how to measure the possible impact of the licensing change here, and wouldn&#8217;t want to ascribe too much weight to it.</p>
<p>(7) Last, the attention of the Wikipedia community <a href="http://creativecommons.org/weblog/entry/8213">ought</a> to have a positive impact on the quality of future versions of Creative Commons licenses (there shouldn&#8217;t be another version until 2011 or so, and hopefully there won&#8217;t be another version after that for much longer). Presumably Wikipedians also would have had a positive impact on future versions of the FDL, but arguably less so given the Free Software Foundation&#8217;s (<a href="http://gondwanaland.com/mlog/2009/02/04/fsf-libreplanet/">excellent</a>) focus on software freedom.</p>
<p>Will any of the above play out in a significant way? How much will it be reasonable to attribute to the license change? Will researchers bother to find out? Here&#8217;s to hoping!</p>
<p>&#8230;</p>
<p>Prior to the Wikipedia community vote on adopting CC BY-SA it crossed my mind to set up several play money prediction market contracts concerning the above outcomes <a href="http://gondwanaland.com/mlog/2006/11/25/iraq-withdrawal-outcomes/">conditioned</a> on Wikipedia adopting CC BY-SA by August 1, 2009, for which I did set up a <a href="http://www.hubdub.com/m28943/Will_Wikipedia_adopt_CC_BYSA_by_August_1_2009">contract</a>. It is just as well that I didn&#8217;t &#8212; or rather if I had, I would have had to heavily promote all of the contracts in order to stimulate any play trading &#8212; the basic adoption contract at this point hasn&#8217;t budged from 56% since the vote results were announced, which means nobody is paying attention to the contract on Hubdub.</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2009/05/31/wikipedia-migration-impact/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Wikipedians against kryptonite</title>
		<link>http://gondwanaland.com/mlog/2009/04/13/wikipedians-against-kryptonite/</link>
		<comments>http://gondwanaland.com/mlog/2009/04/13/wikipedians-against-kryptonite/#comments</comments>
		<pubDate>Mon, 13 Apr 2009 17:51:48 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=710</guid>
		<description><![CDATA[digg_url = 'http://creativecommons.org/weblog/entry/13967'; As mentioned previously incompatible widely used copyleft licenses are kryptonite to the efficacy of copyleft. If you&#8217;ve made 25 or more edits* to a Wikimedia project, you can vote to liberate Wikipedia from this kryptonite. Vote now, instructions and much more background on the Creative Commons blog. Original poster by Brianna Laugher [...]]]></description>
			<content:encoded><![CDATA[<p style="float:right; padding:10px"><script type="text/javascript">
digg_url = 'http://creativecommons.org/weblog/entry/13967';
</script><br />
<script src="http://digg.com/tools/diggthis.js" type="text/javascript"></script><br />
<noscript><a href="http://digg.com/submit?url=http://creativecommons.org/weblog/entry/13967"><img src="http://digg.com/img/badges/100x20-digg-button.png" width="100" height="20" alt="Digg!" /><br />
</a></noscript></p>
<p>As <a href="http://gondwanaland.com/mlog/2007/12/01/copyleft-pd/">mentioned</a> <a href="http://gondwanaland.com/mlog/2008/12/17/cc6/">previously</a> incompatible widely used copyleft licenses are kryptonite to the efficacy of copyleft. If you&#8217;ve made 25 or more edits<sup>*</sup> to a Wikimedia project, you can vote to liberate Wikipedia from this kryptonite. Vote now, instructions and much more background <a href="http://creativecommons.org/weblog/entry/13967">on the Creative Commons blog</a>.</p>
<p><a href="http://en.wikipedia.org/wiki/Special:SecurePoll/vote/1"><img src="http://creativecommons.org/wp-content/uploads/2009/04/propaganda_poster_for_wikimedia_licensing_vote_-_vote_yes_for_licensing_sanity.png"/></a><br /><small><a href="http://commons.wikimedia.org/wiki/File:Propaganda_poster_for_Wikimedia_licensing_vote_-_vote_yes_for_licensing_sanity.svg">Original</a> poster by <a href="http://brianna.modernthings.org/article/196/vote-yes-for-licensing-sanity">Brianna Laugher</a> / <a href="http://creativecommons.org/licenses/by/3.0/">CC BY</a></small></p>
<p><sup>*</sup> My favorite interview question for any <a href="http://creativecommons.org/about/opportunities">position</a> at Creative Commons goes something like &#8220;tell me about your experiences with editing Wikipedia&#8221; which serves the dual purposes of testing whether the candidate knows how to use a computer (you&#8217;d be surprised) and has any practical clue about the types of collaboration Creative Commons&#8217; work facilitates.</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2009/04/13/wikipedians-against-kryptonite/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>CC6+</title>
		<link>http://gondwanaland.com/mlog/2008/12/17/cc6/</link>
		<comments>http://gondwanaland.com/mlog/2008/12/17/cc6/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 09:50:20 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Economics]]></category>
		<category><![CDATA[Intellectual Protectionism]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Politics]]></category>
		<category><![CDATA[Prediction Markets]]></category>
		<category><![CDATA[Public Domain]]></category>
		<category><![CDATA[Public Goods]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=614</guid>
		<description><![CDATA[December 16 marked six years since the release of the first Creative Commons licenses. Most of the celebrations around the world have already taken place or are going on right now, though San Francisco&#8217;s is on December 18. (For CC history before 2002-12-16, see video of a panel recorded a few days ago featuring two [...]]]></description>
			<content:encoded><![CDATA[<p>December 16 marked six years since the release of the first Creative Commons licenses. Most of the celebrations <a href="http://wiki.creativecommons.org/Birthday_Party_2008">around the world</a> have already taken place or are going on right now, though <a href="http://creativecommons.org/weblog/entry/11361">San Francisco&#8217;s is on December 18</a>. (For CC history before 2002-12-16, see <a href="http://cyber.law.harvard.edu/node/4832">video of a panel recorded a few days ago featuring two of CC&#8217;s founding board members and first executive director</a> or read the book <em><a href="http://www.viralspiral.cc/">Viral Spiral</a></em>, available early next year, though my favorite is <a href="http://lists.w3.org/Archives/Public/www-archive/2002Feb/0011.html">this email</a>.)</p>
<p>I&#8217;ve worked for CC since April, 2003, though as I say in the header of this blog, <em>I don&#8217;t represent any organization here. </em>However, I will use this space to ask for your support of my and <a href="http://creativecommons.org/about/people">others&#8217;</a> work at CC. We&#8217;re nearing the end of our fourth annual fall public fundraising campaign and about halfway to our goal of raising US$500,000. We really need <a href="http://support.creativecommons.org/join">your support</a> &#8212; past campaigns have closed out with large corporate contributions, though one has to be less optimistic about those given the financial meltdown and widespread cutbacks. Over the longer term we need to steadily decrease reliance on large grants from visionary foundations, which still contribute the majority of our funding.</p>
<p>Sadly I have nothing to satisfy a <a href="http://gondwanaland.com/mlog/2008/11/02/futarchist-voter-guide/">futarchist</a> donor, but take my sticking around as a small indicator that investing in Creative Commons is a highly leveraged way to create a <a href="http://gondwanaland.com/mlog/2004/10/14/world-intellectual-freedom-organization/">good future</a>. A few concrete examples follow.</p>
<p><a href="http://en.wikipedia.org/wiki/RDFa" rel="tag">RDFa</a> became a W3C Recommendation <a href="http://creativecommons.org/weblog/entry/10095">on October 14</a>, the culmination of a 4+ year effort to integrate the <a href="http://gondwanaland.com/mlog/2007/11/21/semantic-www/">Semantic Web and the Web that everyone uses</a>. There were several important contributors, but I&#8217;m certain that it would have taken much longer (possibly never) or produced a much less useful result without CC&#8217;s leadership (our motivation was first to describe CC-licensed works on the web, but we&#8217;re also now using RDFa as infrastructure for building decoupled web applications and as part of a strategy to <a href="http://sciencecommons.org/projects/data/">make all scientific research available and queryable as a giant database</a>). For a pop version (barely mentioning any specific technology) of why making the web semantic is significant, watch <a href="http://www.ted.com/index.php/talks/kevin_kelly_on_the_next_5_000_days_of_the_web.html">Kevin Kelly on the next 5,000 days of the web</a>.</p>
<p><a href="http://creativecommons.org/weblog/entry/11544">Wikipedia seems to be on a path to migrating to using the CC BY-SA license</a>, clearing up a major legal interoperability problem resulting from Wikipedia starting before CC launched, when there was no really appropriate license for the project. The GNU FDL, which is now Wikipedia&#8217;s (and most other Wikimedia Foundation Projects&#8217;) primary license, and CC BY-SA are both copyleft licenses (altered works must be published under the same copyleft license, except when not restricted by copyright), and incompatible widely used copyleft licenses are <a href="http://gondwanaland.com/mlog/2007/12/01/copyleft-pd/">kryptonite to the efficacy of copyleft</a>. If this migration happens, it will increase the impact of Wikipedia, Creative Commons, free culture, and the larger movement for free-as-in-freedom on the world and on each other, all for the good. While this has basically been a six year effort on the part of CC, FSF, and the Wikimedia Foundation, there&#8217;s a good chance that without CC, a worse (fragmented, at least) copyleft landscape for creative works would result. Perhaps not so coincidentally, I like to <a href="http://www.slideshare.net/mlinksva/how-far-behind-free-software-is-free-culture-presentation" title="see slide 33">point out</a> that since CC launched, there has been negative <a href="http://en.wikipedia.org/wiki/License_proliferation" rel="tag">license proliferation</a> in the creative works space, the opposite of the case in the software world.</p>
<p>Retroactive copyright extension cripples the <a href="http://gondwanaland.com/mlog/2006/11/26/embrace-public-domain/">public domain</a>, but there are relatively unexplored options for increasing the <i>effective</i> size of the public domain &#8212; <a href="http://www.slideshare.net/mlinksva/creative-commons-public-domain-legal-tools-and-infrastructure-presentation">instruments</a> to increase certainty and findability of works in the public domain, to enable works not in the public domain to be effectively as close as possible, and to <a href="http://sciencecommons.org/projects/publishing/open-access-data-protocol/">keep facts in the public domain</a>. CC is pursuing all three projects, worldwide. I don&#8217;t think any other organization is placed to tackle all of these thorny problems comprehensively. The public domain is not only tremendously important for culture and science, but the only aesthetically pleasing concept in the realm of intellectual protectionism (because it isn&#8217;t) &#8212; sorry, copyleft and other public licensing concepts are just necessary hacks. (I already said I&#8217;m giving my opinion here, right?)</p>
<p>CC is doing much more, but the above are a few examples where it is fairly easy to see its delta. CC&#8217;s <a href="http://sciencecommons.org">Science Commons</a> and <a href="http://learn.creativecommons.org">ccLearn</a> divisions provide several more.</p>
<p>I would see CC as a wild success if all it ever accomplished was to provide a counterexample to be used by those who fight against efforts to cripple digital technologies in the interest of protecting ice delivery jobs, because such crippling harms science and education (against these massive drivers of human improvement, it&#8217;s hard to care about marginal cultural production at all), but I think we&#8217;re on the way to accomplishing much more, which is rather amazing.</p>
<p>More abstractly, I think the role of creating &#8220;commons&#8221; (what CC does and free/open source software are examples) in nudging the future in a good direction (both discouraging bad outcomes and encouraging good ones) is horribly underappreciated. There are a bunch of angles to explore this from, a few of which I&#8217;ve <a href="http://www.slideshare.net/mlinksva/the-future-of-digital-freedom-presentation">sketched</a>.</p>
<p>While CC has some pretty compelling and visible accomplishments, my guess is that most of the direct benefits of its projects (legal, technical, and otherwise) may be thought of in terms of lowering transaction costs. My guess is those benefits are huge, but almost never perceived. So it would be smart and good to engage in a visible transaction &#8212; <b><a href="http://support.creativecommons.org/join">contribute to CC&#8217;s annual fundraising campaign.</a></b></p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2008/12/17/cc6/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>25 years of GNU</title>
		<link>http://gondwanaland.com/mlog/2008/09/02/25-years-of-gnu/</link>
		<comments>http://gondwanaland.com/mlog/2008/09/02/25-years-of-gnu/#comments</comments>
		<pubDate>Tue, 02 Sep 2008 20:27:16 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[Intellectual Protectionism]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Peeves]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=565</guid>
		<description><![CDATA[The GNU project turns 25 on September 27. Not much to add beyond what I wrote on the Creative Commons blog. Watch the Freedom Fry video. I do have some meta commentary&#8230; The video, featuring British humorist Stephen Fry, is very British. That is, Americans might wonder if there is any humor in it at [...]]]></description>
			<content:encoded><![CDATA[<p>The <a rel="tag" href="http://en.wikipedia.org/wiki/GNU_Project">GNU project</a> turns 25 on September 27. Not much to add beyond <a href="http://creativecommons.org/weblog/entry/9112">what I wrote on the Creative Commons blog</a>. Watch the <a href="http://www.gnu.org/fry/"><em>Freedom Fry</em> video</a>.</p>
<p>I do have some meta commentary&#8230;</p>
<p>The video, featuring British humorist <a rel="tag" href="http://en.wikipedia.org/wiki/Stephen_Fry">Stephen Fry</a>, is very British. That is, Americans might wonder if there is any humor in it at all. I&#8217;m fine with that.</p>
<p>It&#8217;s great that the video is posted in Ogg Theora format and works seamlessly in my browser via <a href="http://en.wikipedia.org/wiki/Cortado_(software)">Cortado</a>, and download links are provided. However, HTML to copy &amp; paste for direct inclusion in a blog post or other web page should also be provided, as is typical for sharing video. I haven&#8217;t tried making such yet, though I should and might.</p>
<p>Finally, there&#8217;s a hidden jab at some in the free software movement in my CC blog post:</p>
<blockquote><p>One of the movements and projects <a href="http://creativecommons.org/weblog/entry/5668">directly inspired by GNU is Creative Commons</a>. <strong>We’re still <a href="http://creativecommons.org/weblog/entry/8051">learning from the free software movement</a>.</strong> On a practical level, all servers run by Creative Commons are powered by GNU/Linux and all of the <a href="http://code.creativecommons.org/">software we develop</a> is free software.</p>
<p>So please join us in wishing the GNU project a happy 25th birthday by <a href="http://www.gnu.org/fry/">spreading a happy birthday video from comedian Stephen Fry</a>. <strong>The video, <em>Freedom Fry</em>, is released under a <a href="http://creativecommons.org/licenses/by-nd/3.0/us/">CC Attribution-NoDerivatives license</a>.</strong></p></blockquote>
<p>Emphasis added. The <a href="http://www.slideshare.net/mlinksva/free-softwarefree-culture-collaboration">free culture/open content world lags the free software/open source world</a> in many respects, one of those being an understanding of what freedoms are necessary. Some from the free software world have pushed Creative Commons to recognize that in many cases culture requires freedoms equivalent to those expected for free software/open source (that&#8217;s the first bolded link above), while some in the free software world (not necessarily the exact same people, but at least people associated with the same organizations) publish documents and videos under terms that do not grant those same freedoms (that&#8217;s the second bolded link above).</p>
<p>The Free Software Foundation has probably published documents under terms roughly equivalent to CC BY-ND probably before CC existed. Currently the footer of <a href="http://fsf.org">fsf.org</a> says:<br />
<blockquote>Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this notice is preserved.</p></blockquote>
<p>Does the FSF really want to reserve the right to use copyright to censor people who might publish derived versions of their texts? They probably are concerned that someone will alter their message so as to be misleading. Perhaps there was some rationale for this pre-web and pre-CC, but now there is not:
<ul>
<li>People can easily see canonical versions by going to fsf.org. (DNS also should obsolete much of trademark as well, but that&#8217;s for another post.)</li>
<li>CC licenses that permit derivatives <a href="http://creativecommons.org/licenses/by/3.0/legalcode">include</a> the following (see 3(b), 4(a), 4(b), and 4(c) for the actual language):
<ul>
<li>Licensor can specify a link to provide for attribution</li>
<li>Derivative works must state how they are altered</li>
<li>Licensor can demand that credit be removed from the derivative</li>
<li>Unfortunately, in some jurisdictions licensor could press &#8220;moral rights&#8221; to censor a derivative considered derogatory</li>
</ul>
</li>
</ul>
<p>So one can pre-clear the right to make adaptations and retain some legal mechanisms to club creators of adaptations (ordered from best practice to distasteful, according to me).</p>
<p>The <a href="http://en.wikipedia.org/wiki/Software_Freedom_Law_Center">Software Freedom Law Center</a> does worse, publishing its website (also, see the <a href="http://www.softwarefreedom.org/blog/2008/sep/02/gnu-birthday/">SFLC post on 25 years of GNU</a>) under CC BY-NC-ND. Do they really want to prohibit commercial use? SFLC (a super excellent organization, as is the FSF!) is dedicated to software freedom, but still it seems silly for them to publish non-software works under terms antithetical to the spirit of free software.</p>
<p>On a brighter note, the FSF is publishing <a href="http://www.gnu.org/fry/happy-birthday-to-gnu-download.html">promotional images for <em>Freedom Fry</em></a> under a <a href="http://freedomdefined.org">free as in free software as applied to cultural works</a> license (CC BY-SA), one of which has already been taken under those terms for use on <a href="http://en.wikipedia.org/wiki/Stephen_Fry">Stephen Fry&#8217;s Wikipedia article</a>. Ah, the <a href="http://intelligentdesigns.net/blog/?p=94">power of free cultural works</a>. :)</p>
<p>Do wish GNU a happy 25th birtday &#8212; <a href="http://www.gnu.org/fry/">watch and spread the video</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2008/09/02/25-years-of-gnu/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>No index.php</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/</link>
		<comments>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comments</comments>
		<pubDate>Tue, 20 May 2008 16:48:34 +0000</pubDate>
		<dc:creator>Mike Linksvayer</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[Peeves]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531</guid>
		<description><![CDATA[On a mailing list I&#8217;m on someone just pointed to no-www.org. It&#8217;s been awhile since I&#8217;ve run across that site (or, before it existed, Slashdot commenters condemning use of TCWWW &#8212; The Cursed WWW), but I strongly agree &#8212; www. in a domain name is pointless. Even worse is index.php in the path. You&#8217;ve taken [...]]]></description>
			<content:encoded><![CDATA[<p>On a mailing list I&#8217;m on someone just pointed to <a href="http://no-www.org/">no-www.org</a>. It&#8217;s been awhile since I&#8217;ve run across that site (or, before it existed,  Slashdot commenters condemning use of TCWWW &#8212; The Cursed WWW), but I strongly agree &#8212; <code>www.</code> in a domain name is pointless.</p>
<p>Even worse is <code>index.php</code> in the path. You&#8217;ve taken the time to publish a website, now take a few minutes to make its URLs less ugly. I&#8217;m not going to bother setting up no-index-php.org, but someone should. However, in the spirit of no-www.org, here are a couple resources for removing <code>index.php</code> from popular software installations:</p>
<ul>
<li><a href="http://codex.wordpress.org/Using_Permalinks">WordPress Codex on using permalinks</a> &#8212; in many cases WordPress will produce the right <code>.htaccess</code> file automatically, but if you have to fiddle, the default behavior of identifying a post in the querystring with an integer (e.g., <code>?p=1913</code>) has a strong appeal, while the &#8220;almost pretty&#8221; option is extremely ugly.</li>
<li><a href="http://www.mediawiki.org/wiki/Manual:Short_URL">MediaWiki Manual:Short URL</a> &#8212; when this page lived on meta.wikimedia.org, it was appropriated called <a href="http://meta.wikimedia.org/wiki/Eliminating_index.php_from_the_url">Eliminating index.php from the url</a>.</li>
</ul>
<p>Please remove <code>index.php</code> from your URLs, or signal that you have no taste, no technical abilities, or both.</p>
<p>Thanks!</p>
]]></content:encoded>
			<wfw:commentRss>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>
