Post Creative Commons

Mozilla $300m/year for freedom

Thursday, December 22nd, 2011

More Mozilla ads by Henrik Moltke / CC BY

Congratulations to Mozilla on their $300m/year deal with Google, which will more than double current annual revenue. I’ve always thought people predicting doom for Mozilla if Google failed to renew were all wrong — others would be happy to pay for the default search position; probably less since Microsoft, Yahoo, and others make less than Google per ad view, but it’d still be a very substantial amount — and the link article hints that a Microsoft bid drove the price up.

There’s always a risk that Mozilla won’t spend the money well, but I’m pretty confident that they will. Firefox is excellent, and in 2011 has gotten more excellent, faster, and I think many of the other projects they’re doing are really important, and on the right track (insofar as I’m qualified to discern, which is not much), for example BrowserID. Even in small and hopelessly annoying things, like licensing, I think Mozilla is doing good. (Bias: Mozilla has donated to my employer.)

I’m no longer enthused about the possibility of huge resources for progress toward Wikimedia’s vision from advertising on Wikipedia. Since I was last on that bandwagon, it has become even less of a possibility in anything but the distant future: Wikimedia’s donation campaigns have gone very well, adequately funding its operating mission, and lack of advertising has become even more part of Wikimedia’s messaging; I’ve also become more concerned (not in particular to Wikimedia) about the institutional corruption risks previously blogged by Peter McCluskey and Timothy B. Lee. (Note these objections don’t apply to Mozilla: its significant revenue has always been advertising-based; very roughly its revenues are already 10x those of Wikimedia’s; and it is also building up an individual donor program, which I agree is often the healthiest revenue for a nonprofit.)

But I still very much think freedom needs massive, ongoing resource infusions, in the right institutional framework. I celebrate the tremendous benefits of the FLOSS community achieves without massive, concentrated, ongoing resource infusions, but I also admit that the web likely would be much worse, much less webby, and much less free without concentrated resources at Mozilla over the last several years.

Thank you Mozillians, and congratulations. I have very high expectations for your contributions over the next years to the web and society, in particular where more freedom and security are obviously needed such as mobile and software services. Such would be just a start. As computation permeates everything, and digital freedom becomes the most important political issue, the resources of many Mozillas are needed. More on that, soon.

Encyclopedia of Original Research

Thursday, December 15th, 2011

As I’m prone to say that some free/libre/open projects ought strive to not merely recapitulate existing production methods and products (so as to sometimes create something much better), I have to support and critique such strivings.

A proposal for the Encyclopedia of Original Research, besides a name that I find most excellent, seems like just such a project. The idea, if I understand correctly, is to leverage Open Access literature and using both machine- and wiki-techniques, create always-up-to-date reviews of the state of research in any field, broad or narrow. If wildly successful, such a mechanism could nudge the end-product of research from usually instantly stale, inaccessible (multiple ways), unread, untested, singular, and generally useless dead-tree-oriented outputs toward more accessible, exploitable, testable, queryable, consensus outputs. In other words, explode the category of “scientific publication”.

Another name for the project is “Beethoven’s open repository of research” — watch the video.

The project is running a crowdfunding campaign right now. They only have a few hours left and far from their goal, but I’m pretty sure the platform they’re using does not require projects to meet a threshold in order to obtain pledges, and it looks like a small amount would help continue to work and apply for other funding (eminently doable in my estimation; if I can help I will). I encourage kicking in some funds if you read this in the next couple hours, and I’ll update this post with other ways to help in the future if you’re reading later, as in all probability you are.

EoOR is considerably more radical than (and probably complementary to and/or ought consume) AcaWiki, a project I’ve written about previously with the more limited aim to create human-readable summaries of academic papers and reviews. It also looks like, if realized, a platform that projects with more specific aims, like OpenCures, could leverage.

Somehow EoOR escaped my attention (or more likely, my memory) until now. It seems the proposal was developed as part of a class on getting your Creative Commons project funded, which I think I can claim credit for getting funded (Jonas Öberg was very convincing; the idea for and execution of the class are his).

A Toolkit for Anti-SOPA Activism: #13 (or #0?)

Monday, December 12th, 2011

The Electronic Frontier Foundation has an excellent checklist of 12 things you can do to fight the U.S. Congress’ attack on the Internet. Most of them are tiresome rearguard actions against this particular legislation (though most can have secondary long-term effects of educating policymakers and the public about the harm of attacking the Internet). All this is necessary, please take action now.

Action #12 is long-term: contribute financially to the EFF so they can continue “leading the fight to defend civil liberties online, so that future generations will enjoy an Internet free of censorship.” Indeed, please do this too. I’ve recommended becoming an EFF member in the past, and will continue to do so. Actually I’m even more enthusiastic about donating to the EFF in 2011 than I was in 2005. In addition to playing an absolutely critical role in fighting SOPA, PIPA, and their ilk, the EFF’s small technical staff is working on some of the most important technical challenges to keeping the Internet open and secure. They are awesome!

There’s one more item that needs to be in every responsible digital freedom activist’s toolkit: the digital commons, meaning free and open source software and their analogues in culture, knowledge, and beyond. Using and consuming free software and culture is crucial to maintaining a free society. There are many reasons, some of which I mentioned recently at OWF, and with a bit more focus in a FSCONS 2008 presentation (slideshare, .pdf, .odp), but here’s one: imagine a world in which most software and culture are free as in freedom. Software, culture, and innovation would be abundant, there would be plenty of money in it (just not based on threat of censorship), and there would be no constituency for attacking the Internet. (Well, apart from dictatorships and militarized law enforcement of supposed democracies; that’s a fight intertwined with SOPA, but those aren’t the primary constituencies for the bill.) Now, world dominationliberation by free software and culture isn’t feasible now. But every little bit helps reduce the constituency that wishes to attack the Internet to possibly protect their censorship-based revenue streams, and to increase the constituency whose desire to protect the Internet is perfectly aligned with their business interests and personal expression.

Am I crazy? Seriously, I’d like to make the case for the commons as crucial to the future of free society more compellingly. Or, if I’m wrong, stop making it. Feedback wanted.

Relatedly, the English Wikipedia community is considering a blackout to protest SOPA. Here’s the comment I left at the request for comment:

Support doing something powerful. I blackout would be that. I do have some reticence though. Making the knowledge in English Wikipedia and maybe other sites inaccessible feels a bit like protestors who destroy their own neighborhood. Sometimes necessary to gain attention and perhaps justice in the long run, but always painful and with collateral victims. Sure, visitors to Wikipedia sites can come back later or find a mirror, but just as surely, the neighborhood will recover. Maybe. Admittedly the analogy is far from perfect, but I wish there were something the Wikimedia movement could do that would have power analogous to a mass physical action, but avoid costs analogous to the same. Long term, I think fulfilling the Wikimedia vision is exactly that. In the short term, maybe a total blackout is necessary, though if there’s a a way to equally powerfully present to viewers what SOPA means, then let them access the knowledge, I’d prefer that. UI challenge? Surely some A:B testing is in order for this important action. I’d hope that at least some messages tested convey not only the threat SOPA poses to Wikimedia, but the long-term threat the Wikimedia movement poses to censorship.

Mozilla Public License 2.0 and increasing public copyright license compatibility

Tuesday, December 6th, 2011

Incompatibility among public copyright licenses dampens their potential for reducing underlying friction caused by copyright. Increasing compatibility among public copyright licenses is one of the successes of the free/libre/open source community, or so I think. Without long-term, distributed collaboration among license stewards and projects released under public licenses, it would have been easy to obtain a world in which it usually isn’t legally possible to use code from one project in another. (A shared understanding of what constitutes “free” and “open” really helps — the scope for incompatible-in-spirit licenses is greatly reduced, and distributed collaboration facilitated by everyone sharing broad premises.)

I’ve been watching from afar development of the Mozilla Public License version 2 (going for nearly 2 years, I believe about the right amount of time to version a widely used public license) almost exclusively because I was eager to see it become GPL compatible, and how it would achieve this.

Luis Villa explained most of the “how” three months ago. To make sure I understand, here’s my summary:

  • MPL 1.1 is not GPL-compatible. MPL 2.0 will be, but with a few caveats to ensure that projects released under the MPL won’t become GPL-compatible unintentionally, and that there’s a way for new projects under MPL 2.0 that really, really don’t want to be GPL compatible, don’t have to be.
  • Code from a project is released under MPL 2.0 (and not multi-licensed), it can only be made available under the GPL* when incorporated into a larger project that is already GPL licensed, i.e., there has to be a good reason.
  • The entity doing such incorporation in the point above has to offer the MPL code under the MPL and additionally the GPL. A downstream entity can choose to only use the GPL. In other words, people who want to use the original project’s code line under the MPL have ample opportunity to do so, until it is truly forked into a GPL-only version.
  • MPL 1.1 projects (1.1 has a “future versions” clause) modified and released under MPL 2.0 are not GPL-compatible in the manner above unless the project was already multi-licensed under the MPL and GPL (the most important MPL 1.1 licensed projects are multi-licensed), i.e., the intent to allow for use under the GPL is already established.
  • Projects that want to use MPL 2.0 and really don’t want to be GPL compatible can include an “Incompatible With Secondary Licenses” notice.

I think the last point is an unfortunate complication (such projects could stick with MPL 1.1, for instance), but I trust that there are good stakeholder use cases for it. But that’s a minor nit. Villa and other people who worked on MPL 2.0 did a great job and get congratulations and thanks from me.

One of my dreams for Creative Commons Attribution-ShareAlike 4.0 is that it be one-way GPL compatible, as MPL 2.0 will be. MPL 2.0 demonstrates mechanisms for achieving GPL compatibility without upsetting current licensor expectations, which ought be a useful perspective from which to evaluate options for CC BY-SA 4.0. Though CC licenses should not be used for code, it’s easy to see a future in which most “culture” includes “code” and it is an unnecessary pain to keep their licenses separate in all cases. Also, there is some demand for a source-requiring copyleft license for non-software works (BY-SA does not require adaptations to provide source, which is often OK for cultural works, but not always) and it doesn’t make sense to create another source-requiring copyleft license in addition to the GPL.

*Actually LGPL 2.1 or greater, GPL 2.0 or greater, or AGPL 3.0 or greater. MPL has a weaker copyleft than any of the GPL-family licenses — MPL’s copyleft is scoped by file, LGPL’s by library, GPL’s by any linked code, AGPL adds requirement for source distribution to network services.

Addendum 20120103: MPL 2.0 is released today. FSF has added MPL 2.0 to their free licenses page with a GPL compatibility explanation.

Tiresome rearguard actions

Wednesday, November 16th, 2011

Watch out 2024!


Incorporates North Korea Mass Games by Peter Crowcroft and Hollywood Sign by Oreos, available under BY-SA (questionably in former case), but I’m claiming fair use. Result dedicated to the public domain.

Commons experts to develop version 4.0 of the CC licenses

Thursday, November 3rd, 2011

As described on the Creative Commons blog some initial discussions were had at the CC Global Summit about 6 weeks ago in Warsaw. I’m looking forward to the start of in depth discovery, analysis, and debate of pertinent issues on the cc-licenses list, the CC wiki, and elsewhere over the coming months. Please join in, commons experts.☺

I gave a brief presentation on one of those issues at the summit, on the “NonCommercial” term of some CC licenses (odp, pdf, slideshare). [Addendum 20111104: This talk was not recorded. Only slides are available. Don’t watch the videos below if you’re only looking for a talk on NC!]

More relevantly (to 4.0; yes, NC is pretty relevant, becoming less so, the commons is super relevant, indeed all important) though more abstractly, I also organized a session on “CC’s role in the global commons movement”. I’m very happy with how that turned out, but it is only a tentative beginning, about which I will write further. For now you can read Silke Helfrich’s summary post and slides, Tyng-Ruey Chuang’s presentation text, Leonhard Dobusch’s slides, and Kat Walsh’s presentation text and download or watch at archive.org or YouTube:

Because I may never get around to blogging it separately, I also gave a presentation on “what’s happened in Creative Commons and the open community over the last 3 years.” You may recognize one slide from an earlier post. View slides (odp, pdf, slideshare) or video at archive.org or YouTube:

Almost Wikipedias and innovation in free collaboration projects

Friday, October 21st, 2011

I recently watched a presentation by Benjamin Mako Hill on Almost Wikipedia: What Eight Collaborative Encyclopedia Projects Reveal About Mechanisms of Collective Action (audio and video at the link) — or some conjectures about why Wikipedia took off, while 7 older English language internet encyclopedia projects did not.

The presentation had some interesting bits of net history, at least to someone as poorly read as myself — I had only heard about Interpedia (1993) and The Distributed Encyclopedia Project (1997) recently via a timeline of distributed Wikipedia proposals.

Through study of materials concerning the older projects and interviews with project founders, Hill arrived at 4 propositions…

  1. Wikipedia attracted contributors because it was built around a familiar product.
  2. Wikipedia attracted contributors because it was focused on substantive content development instead of technology.
  3. Wikipedia attracted contributors because it offered low transaction costs to participation.
  4. Wikipedia attracted contributors because it deemphasized attribution and “social ownership” of content.

…mapped on a grid reminiscent of many diagrams of “innovation quadrants” (example):

Or, as Dan O’Sullivan said with a broader stroke, ‘Everything is radical about Wikipedia except for the actual articles’.

At first blush this indicates that I should temper my enthusiasm for claiming that Wikipedia exploded the category of encyclopedias and that more free collaboration projects should aim to explode additional product categories.

Though early Wikipedians set out to create an , and I’m persuaded that presenting contributors with a familiar product to build helped it succeed, I think it is clear that Wikipedia, or more properly 845 language Wikipedias and other Wikimedia projects, have created a “product” that is much more useful and different from previous encyclopedias in ways that justify saying it has “exploded” the category. Yes, individual articles read more or less like previous encyclopedia articles, but then emails read more or less like letters. One approach to thinking about how big of an impact Wikipedia may have made so far would be to compare Wikipedia to surviving proprietary online encyclopedias (or perhaps hypothetical ones, had Wikipedia or similar never happened). I suspect the comparison would be akin to AOL and near peers vs. the internet.

One remain hopeful about free collaboration exploding further categories is that Wikipedia, and of course free and open source software projects, have innovated on process. There’s a huge amount of knowledge diffusion to be done, and further development of free collaboration processes, but a now new free collaboration project doesn’t automatically start out in a dead zone of innovating in too many dimensions if it attempts to include product innovation, as might have been the case in the past, as free collaboration equaled process innovation.

One small thing that we’ve mostly figured out that we mostly hadn’t figured out 10+ years ago (or 20+ years ago for software) is appropriate copyright licensing. I dimly recall from the past reading about copyright issues with keeping h2g2 going, and limitations for everything2 (no license is required, so entries are mostly solo-contributor), but I quickly looked at a few of the other projects Hill mentioned and found some curiosities. Interpedia’s FAQ on copyright doesn’t say what the project’s copyright policy is, but does express fear of an infamous patent. The Distributed Encyclopedia Project used what would now be recognized as an onerous and impractical license that at a glance I’m not sure agrees with the brief statement found at the bottom of an example article. The very first archive.org capture of theinfo.org states “All of the content is released under the Anti-Copyright License”, which sounds hopeful, though subsequent captures don’t have that statement, and the text of said license is not captured.

I’m really looking forward to Hill’s publication, as well as the further development of his research program concerning mass collaboration and social movements. Also, check out his reading list on AcaWiki.

Open World Forum: Knowledge Commons Fail/Fix

Thursday, October 13th, 2011

A few weeks ago I gave a talk at Open World Forum. Slides (odp, pdf, slideshare), video (archive.org, YouTube):

I rushed through my final slides and promised to expand on them virtually, which I’ve done here with more slides (odp, pdf, slideshare), or watch a video narration of same (archive.org, YouTube):

Thanks to Open World Forum co-president Louis Montagne and Knowledge Commons track leader Florence Devouard for inviting me to participate!

7 FLOSS trends of the past 37.5 months

Monday, September 12th, 2011

A prospective, from memory, high level summary of trends in Free/Libre/Open Source Software, in the last 37.5* months:

Design. Many major free software projects have turned in some form to design[er]-driven UX/UI/look-and-feel/etc. Not all (any?) are acclaimed successes yet, but in a few years “open design” may go from paradoxical to hot.

Diversity. Lack thereof has become recognized as a major impediment to FLOSS potential. Existing cultures will change as participation expands and vice versa.

Distributed version control systems. Have changed the way many developers and projects work.

Governance. “Open by rule” governance that treat all participants equally and are run transparently has become recognized as a crucial part of making FLOSS FLOSSY, in addition to (and congruent with) FLOSS licensing. However, some advocate for corporate (usually) controlled projects in order to obtain corporate resources for FLOSS development. GPLv3 has seen strong uptake.

Mobile. Unlike the desktop a mostly free system (Android) is very popular, but also unlike the desktop, mobile devices with approaching 100% FLOSS[Y] software more or less don’t exist. The “appstore” phenomena is recognized as a threat to FLOSS, but it is totally unclear how that will play out.

Net services. Apart from Wikipedia, none of the dominant services people access through the web are free software. Most are largely powered by free software, and companies that run the services contribute much to back-end software, but the services users directly access are proprietary and centralized, with no interoperability among them. FLOSS and federated social web services have made strides but there is much significant technical work to do, and the network effects of the dominant proprietary services are daunting.

Open web. In 2008, Firefox 3 had just been released and Flash was ubiquitous. The “open web” is in much better shape now. It is the platform with the most innovation, is almost entirely based on open standards. As of fairly recently, the prognosis even for open web video looks good. One of the leading browsers, Firefox, is free software, and the free software WebKit renderer powers most others, while IE slowly declines.

I’ve surely missed things, some intentionally (patent threat), some out of partial ignorance (e.g., I don’t have any sense of how much has changed in the last 3 years for FLOSS as a grant, procurement, regulatory, or other “policy” requirement, but know it could be important).


*37.5 months ago Creative Commons held its previous global meeting. Another will be held next week. I’m organizing 2.33** sessions, one of which will touch on movements near Creative Commons (“Where are We?”) and another of which concerns these in depth (or as much as is possible in 80 minutes; “CC’s Role in the Global Commons Movement”).

The CC-specific parts of these sessions will be fairly detailed and for the first one, possibly more interesting to insiders (many of the participants have been involved in CC affiliate projects for most of CC’s history).

I’d also like to convey, perhaps in as little as one slide, the big trends of the last 3 years in a few related areas, without any details. These areas and their trends lead, inform, reinforce, and depend on CC’s work in varying measures, so I think the CC community should understand them at a high level at least, such that the most relevant can be more closely learned from or cooperated with.

**I’m also organizing 1/3 of a session on issues to consider for version 4.0 of the CC license suite; the part I’m organizing concerns the non-commercial clause used by some of those licenses. I promise it will be much more fun than a report on that topic.

Essential Of Life+

Monday, September 12th, 2011

Killing bad products is essential to the health of a product line. “Bad” might mean defective, poor fit, or even merely unpopular.

I’m happy to report again that Creative Commons is retiring two little used licenses, with a fairly thorough explanation of the history and problems of those bad products.