Post Commons

Democratizing Wikimedia Innovation

Wednesday, May 27th, 2015

Through the end of this month the Wikimedia community is electing 3 members of the Wikimedia Foundation board. You qualify to vote if you’ve made at least 300 edits before April 15 and 20 between October 15 and April 15 to any Wikimedia project.

If you don’t quality to vote, it won’t be hard to do so for next time if you get started now: Log in or create an account and be bold when you see a typo, incorrect or missing information in a Wikipedia article. Familiarize yourself with Wikipedia’s sibling projects; edits to any of them count. Play the Wikidata Game. I heartily recommend doing these things as a matter of learning and sharing knowledge regardless of desire to vote in Wikimedia elections or lower threshold and more fun votes such as for the Wikimedia Commons Picture of the Year. The current election is just an excuse for inserting this Public Service Announcement. ;-)

If you do qualify to vote, please do. I voted for Denny Vrande?i? and give him the strongest possible endorsement. I also voted for and endorse James Heilman.

The election uses approval/disapproval ratio to determine winners, so disapproval votes are powerful. I made a few but don’t want to publish because frankly all of the candidates are excellent and extremely qualified for a Wikimedia Foundation community board seat.

community-centered theory of changeThe central issue in this election is evident in the Candidate statements, discussion, structured Q&A (1, 2, 3, 4), in a series of blog posts by Pete Forsyth (who was briefly a candidate but stepped aside), and outside the context of the current election, in blog posts by Lane Raspberry and Nimish Gautam., and the one message I’ve sent on the issue, which the first paragraph of Vrande?i?’s candidate statement sums up:

Wikimedia is a modern wonder – and yet, it must change: most of our projects, as they are today, cannot truly succeed. To achieve our mission, we must increase the effectivity of every single contributor. At the same time, the communities are often seen as change resistant – but falsely so: they do welcome change, done right, as I have shown with Wikidata.

Along these lines, I especially commend Vrande?i?’s and Heilman’s answers to the following Q&A topics: Use of Superprotect and respect for community consensus, Retaining current volunteers versus recruiting new ones, Improving content, and Diversity and scope.

It’s commonplace for central organizations (of which I am a fan) to neglect or denigrate communities they serve, whether the relationship is one of collaboration, constituency, or consumption. Sometimes a version of neglect is even the right behavior, e.g., a product or project with some users may need to be EOL’d. But most organizations could do much better. It is essential that the Wikimedia Foundation do so, as the people who edit or otherwise contribute to the various Wikimedia projects are its key competitive advantage. If Wikimedia and other commons-based peer production projects are to stay relevant, nevermind helping achieve world liberation, they need to figure out how to become more effective, starting with embracing the idea that most of the vision and innovation needed to do so will come from the community, not the central organizations, and implementation done in partnership with the community.

Unrelated to the community issue, I’ve previously blog cheered Vrande?i?’s and Heilman’s work on Wikidata and Wikipedia/medical journal collaboration respectively.

Tangential ex-Wikimedia Foundation links:

I was very sad to read that Erik Moeller recently left the foundation, where he was Deputy Director. Though he seemed to endorse the organization/community vision dichotomy (my one message linked above is a mailing list reply to him), in my view he is perhaps the best example in the Wikimedia universe of community vision — he had written about and many cases prototyped most of the innovations the foundation is still working on implementing, many years later, before becoming an employee.

Moeller has since started a podcast, interviewing another ex-Wikimedia Foundation person, Sumana Harihareswara, for the first episode.

Harihareswara has two recent posts on Crooked Timber, Codes of conduct and the trade-offs of copyleft and Where are the women in the history of open source? I found them both very interesting and left comments.

Former Wikimedia Foundation Executive Director Sue Gardner is now “developing a strategic plan for and with the Tor Project” and separately researching “the broader state of ‘freedom tech’ ― all the tools and technologies that enable free speech, free assembly, and freedom of the press.” That’s great news; Tor and other ‘freedom tech’ tools are incredibly exciting and important. But, a moment of critical cheering: as I noted around the time Gardner stepped down as WMF ED, I’m inclined to think that re-routing the knowledge economy is even more important than tools that can route around censorship for a good future. The former is what Wikimedia projects do.

Hello World Intellectual Freedom Organization

Saturday, April 25th, 2015

Today I’m soft launching an initiative that I’ve been thinking about for 20 years, obtained a domain name for in 1998, blogged about once in 2004, and the last few years have been exploring on this blog without naming it. See the first items in my annual thematic doubt posts for 2013 and 2014: “protecting and promoting intellectual freedom, in particular through the mechanisms of free/open/knowledge commons movements, and in reframing information and innovation policy with freedom and equality outcomes as top.”

I call it the World Intellectual Freedom Organization (WIFO).

Read about its theory, why a new organization, proposed activities, and how you can help/get involved.

Why today? Because April 26 is World Intellectual Freedom Day, occupying and displacing World Intellectual Property Day, just as intellectual freedom must occupy and displace intellectual property for a good future. Consider this 0th World Intellectual Freedom Day another small step forward, following last year’s Without Intellectual Property Day.

Why a soft launch? Because I’m eager to be public about WIFO, but there’s tons of work to do before it can properly be considered launched. I’ve been getting feedback from a handful of people on a quasi-open fellowship proposal for WIFO (that’s where the activities link above points to) and apologize to the many other people I should’ve reached out to. Well, now I’m doing that. I want your help in this project of world liberation!

Video version of my proposal at the Internet Archive or YouTube. My eyes do not lie, I am reading in an attempt to fit too much material in 5 minutes.

I’ll probably blog much less here about “IP” and commons/free/libre/open issues here from now on, especially after opening a WIFO blog (for now there’s a Discourse forum; most of the links above point there). Not to worry, I am overflowing with idiosyncratic takes on everything else, and will continue to post accordingly here, as much as time permits. ?

Be sure to celebrate the 0th World Intellectual Freedom Day, even if only momentarily and with your lizard brain.

Apple watch

Monday, March 9th, 2015

Apple Watch official logoApple epitomizes the future we’re choosing by way of treating knowledge as property: gross inequality and hierarchical control, but amazing, such that it is hard to imagine a different arrangement. (I argue very different arrangements concerning knowledge are possible and some would produce much better outcomes — freedom and equality — and some would produce much worse, but still be considered amazing, as they would be relative to the past — knowledge policy is a point of incredible leverage in either direction.)

I don’t watch Apple closely at all, but occasionally a headline catches my eye, as two have recently.

  • Android share of smartphone profits plummets to 11 percent. 89% of smartphone profits go to Apple, despite shipping only 19.7% of smartphones. Of course there are other contributing factors, but these numbers suggest to me something about the surplus obtained by producers and consumers in the case of proprietary (iOS) and open source (Android) operating systems, and the resulting concentration of wealth toward owners of the former.
  • Apple Is Now More Than Double the Size of Exxon―And Everyone Else. That’s by market capitalization, around $750 billion. As the article notes, IBM in 1983-1985 had more than double the market cap of any other company. Knowledge as property driven wealth concentration is not at all new, but I suspect it is increasing as knowledge becomes unambiguously the commanding heights and we shift from an industrial to a knowledge economy (transition captured in pithy phrases such as “data is the new oil” and “software is eating the world”) and knowledge is increasingly subject to various freedom infringing (intellectual property) regimes, and I suspect that more people are recognizing this.

In the more people department, I’ve noticed in the last day:

Now these two are largely making stereotypical contemporary political points for or against state activity respectively (the latter by proxy of claiming Democrats don’t really care about inequality) and not demanding a fundamental shift away from property as the regime governing knowledge (the former demands a ‘golden share’ of intellectual property derived profits for the state). But I’d be very happy to see both “sides” embrace such a shift. Demanding that government and government-funded knowledge not be treated as property is a good start.


My ironic edit of 5 reasons you should never buy an Apple Watch, pointing out that control and inequality appear to be marvelous.

6 reasons for GPL lovers, haters, exploiters, and others to enjoy and support GPL enforcement

Thursday, March 5th, 2015

Linux kernel developer Christoph Hellwig today filed a lawsuit against VMware (NYSE:VMW; US$36 billion market cap) due to their long time refusal to observe the terms of the GPL when incorporating code by Hellwig into their kernel, which remains proprietary. If VMware observed the GPL’s terms, their kernel including all source would be released under the GPL. This is a significant case, in part due to the rarity of GPL enforcement lawsuits. Details on the website of Software Freedom Conservancy, which is coordinating and funding (you can help) this action.

If the GPL is rarely enforced, its differentiation from non-copyleft licenses such as MIT, BSD, and Apache is muted. Why should you support license differentiation and thus GPL enforcement?

  1. You think copyleft is a wonderful hack, a productive and even necessary strategy for protecting and expanding the software commons. No enforcement makes the hack buggy: rarely executing and easily circumvented. So of course you want enforcement.
  2. You think copyleft curtails freedom, and ironically hampers the software commons — intractable incompatibility means software can’t be freely mixed, and the attempt to prevent capture by proprietary software interests only abets capture of the field by intellectual parasite lawyer interests. Your efforts to persuade developers and companies that they should avoid GPL software at all costs (up to reimplementation) in preference to permissive and public domain instruments can only be enhanced by prominent GPL enforcement by lawsuit.
  3. You think copyleft is great for software business, as one can acquire users by offering GPL software, then acquire customers by shaking down users who could conceivably not be observing the GPL to the letter. Public GPL enforcement makes your salespeople more compelling.

Among people who have any opinion about copyleft, I’m pretty sure there are very few who accept more than one of the above thoughts. I enjoy all three (the third looks like a sin tax to me). My point here is that people who completely disagree on the purpose and efficacy of copyleft ought all be excited and supportive of copyleft enforcement. But there are additional, less commonly discussed reasons:

  1. You think strong copyleft encourages more people to release free software, people who would not be comfortable with releasing under a non-copyleft license, whether because they fear piracyproprietarization more than obscurity (some overlap with 1 above), or because they want to make wealthy entities pay (lots of overlap with 3 above). Strong copyleft serves as the NonCommercial of the software world (without being fundamentally broken like NC, though the most radical believers in 2 above might disagree) in that it increases the range of licensing options to meet the preferences of both those who fear exploitation by business, and those who want to exploit business. Strong copyleft isn’t so strong without enforcement, so anyone who understands the value of this differentiation should want it to be strengthened by enforcement actions.
  2. You think copyleft-for-x is needed for some non-software field (or hear such thoughts expressed; e.g., for seeds or hardware designs, even real property), but the details of how copyleft works are a bit fuzzy. Enforcement by lawsuit is where the rubber meets the road, so you should enjoy the demystification provided by such actions and support them. Also, successful copyleft enforcement will stoke more people to have desires for copyleft-for-x, thus increasing your community of people intent on figuring out the “for-x” part.
  3. You think copyleft is most usefully considered as a prototype for and test of rules that ought be enforced by more effective regulatory mechanisms. Whether you think software provided without source and permissions should be totally banned, not regulated at all, or only regulated for particular uses or in particular fields (e.g., products and services already subject to other safety, disclosure, and pro-competition or consumer protection requirements), it is absurd to think that developer whim and resources in applying and enforcing the GPL regulates and regulates effectively an optimal set of software. It is time to move beyond debate of a hack of state-deputized private censorship as central to software freedom politics and policy, and on to debating directly state vs. market regulation of software (with all the usual arguments about (in)adequacy of market provision and harm/help of state intervention) as in any field of importance, preferably with very strong commons-favoring bias from both sides (e.g., software freedom market-skeptics and state-skeptics ought agree that regulation by private censorship, which serves proprietary interests almost exclusively, be wound down, and that state entities self-regulate by mandating software freedom for everything they acquire and fund). Unenforced copyleft means the rules prototyped are untested, reducing salience of the prototype, so you also should enjoy GPL enforcement actions.

I enjoy these latter 3 reasons especially, perhaps especially because few other people seem to (I’m eager to be or become wrong about this).

Go help Software Freedom Conservancy support Hellwig’s enforcement against VMware, or tell me why I’m wrong. Note I’m on Software Freedom Conservancy’s board and endorse all of their work, but as usual, this blog post represents only my opinion. Of the reasons to support enforcement above, they’d agree with 1; probably find 2 and 3 and maybe 4 objectionable; 5 and 6 perhaps curious but distant from work in today’s trenches. Again, my point is that many more people than those who agree with 1 (copyleft for good), even those who totally disagree with 1, should enjoy and support GPL enforcement.

The lawsuit will probably be heavily covered in the technology press, but you can read some early discussions now at LWN.net, Hacker News, and reddit. You can also read about copyleft in general at copyleft.org (another Software Freedom Conservancy project; my take).

Annual thematic doubt 2

Tuesday, February 17th, 2015

My second annual thematic doubt post, expressing doubts I have about themes I blogged about during 2014.

commons ? freedom, equality ? good future

Same as last year, my main topic has been “protecting and promoting intellectual freedom, in particular through the mechanisms of free/open/knowledge commons movements, and in reframing information and innovation policy with freedom and equality outcomes as top.”

Rather than repeating the three doubts I expressed last year under the heading “intellectual freedom” (my evaluation of these has not much changed), I will take the subject from a different angle: the “theory of change” I have been espousing. This theory is not new to me. Essentially it is what attracted me to following the free software movement circa 1990 — its potential of extensive, pro-freedom socio-economic reform from the bottom up. That and wanting to run a unix-like on my computer — a want satisfied without respect to freedom as soon as I could use a Sun workstation at work, and for many years now would have been satisfied by OS X. I never cared very much about being able to read, modify, and share all of the software on my computer — the socio-economic implications of those capabilities make them interesting, to me. The claimed ends of the theory are in the ‘for a good future’ slogan I’ve occasionally used at least since 1998. I occasionally included the theory in blog posts (2006) and presentations (2008). Much of my ‘critical cheering’ last year (doubt) and before has largely been about my perhaps unreasonable wish that ‘free/open’ organizations and movements would take the theory I do and act as I think follows. I could easily be wrong on the theory or best actions it implies. Accordingly, I ratcheted down critical cheering in 2014; hopefully most but not all of what remained was relatively fun or novel. Instead I focused more sharply on the theory, e.g., in Sleepwalking past Freedom’s Commons, or how peer production could increase democracy, equality, freedom, and innovation, all of them!

The theory could be attacked from a number of angles — I’d love to see that done and learn of new vulnerabilities. For example, commons might not significantly affect freedom and equality, these may not be the right values, and one might consider a ‘good future’ to be one with maximum hierarchy, spectacle, even war (I repeatedly argue that future tech and culture will be marvels in most plausible futures, and that is a reason to reject ones that do not have freedom and equality as top values, but also something that makes it hard to see how a future — or present — could be different or better with more knowledge economy/policy-driven freedom and equality). But this isn’t a cheap refutation post (see below) and I don’t have very practical doubts about those values and what they imply constitutes a good future.

But I do have practical doubts about the first leg of the theory. Summary of that leg before getting to doubts: Commons-based knowledge production simultaneously destroys rents dependent on freedom infringing regimes, diminishing the constituency for those regimes, grows the constituency and policy imagination for freedom respecting regimes, and not least, directly increases freedom and equality.

Doubts:

  • Effects could be too small to matter, or properly attributed to generational or other competition among firms, not commons-based production. Consider Wikipedia, a success of commons-based production if there is one. Such success may not be possible in other sectors, especially ones that command top policy attention (drugs and movies) — policy imagination has not been increased. The traditional encyclopedia industry was already mostly destroyed by Microsoft Encarta when Wikipedia came along. The encyclopedia industry was not a significant constituency for freedom infringing regimes, so its destruction matters not for future policy. Encyclopedias were readily accessible at libraries, vastly more useful info of the sort found in encyclopedias is accessible online now, excluding Wikipedia, and ‘freedoms’ to modify and distribute are just not relevant nearly all humans.
  • I claim that the best knowledge policy reform is that which favors commons and that the reforms traditionally proposed by copyright and patent reformers are relatively futile because such proposals if implemented would not significantly change the knowledge economy to produce freedom and equality nor grow the constituencies for such changes — rather they are just about who, how, and for how much the outputs of production under freedom infringing regimes may be used — so-called balance, not the tilt I demand. But perhaps the usual set of reform proposals is the best that can be hoped for, especially given decades of discourse and organization-building around those proposals, and almost none about commons-favoring reform. Further, perhaps the usual set of reform proposals is best without qualification — commons-based production is a culturally marginal (in software; wholly irrelevant in most other sectors) arrangement that ought be totally ignored by policy.
  • Various (sometimes semi-) free/open movements within various sectors (e.g., software, education, research publication) are having some policy successes, without (as far as I know) usually considering themselves to be as or more central to shaping knowledge policy as usual things fitting under ‘copyright reform’ and ‘patent reform’ but this could be just what needs to happen. The important thing is that commons-based knowledge production entities act to further their interests with minimal distance from current policy discourse, not that they have any distracting and possibly discrediting theory about doing so relative to overall knowledge policy.

Only the first of these gives me serious pause, though my discounting the last two might be a matter of (dis)taste — my feeling is that most of the people involved thoroughly identify with the trivia of copyright, patent, and similar law, even if they think those laws need serious reform, and act as if commons-based production is something to be protected from reform in the bad direction, but not at all central. Sadly if my feeling is accurate, the second and third doubts probably ought give me more pause than they do.

Despite these doubts, the potential huge win-win (freedom and equality, without conflict) of reorienting the knowledge economy and policy around commons-based production makes robust discourse (at the least) on this possibility urgent, even if tilt probability is low. One of the things that makes me favor this approach is that reform can be very incremental — indeed, it is by far the most feasible reform of any proposed — we just need a lot more of it. Push-roll towards tilt!

The most damning observation is perhaps that I’m only talking, and mostly on this very blog. I should change my ways, but again, this is not a cheap refutation post.

Software Freedom/Futurism/Science Fantasy

I recently wrote that “it’s much easier to take software freedom as a serious issue of top importance if one has a ‘futurist’ bent. This will also figure in a forthcoming post from me casting doubt on everything in this post and the rest from 2014.”

How important are computers to human arrangements, and how large is the range of plausible computer-involved arrangements, and how much can those realized be changed? Should anyone besides programmers and enthusiasts care about software specifically, any more or less than they care about the conditions under which any tool is created and distributed? (Contrast with other tools would be good here, but I’ll leave for another time.)

The vast majority of people seem to treat software as any other tool — they want it to work as well as possible, and to be as cheap as possible, the only difference being that their intuitions about quality and cost of software may be worse than their intuitions for the quality and cost of, for example, bridges. Arguably nearly everyone has been and perhaps still is correct.

But one doesn’t need to be much of a futurist to see software getting much more important — organizations good at using software ‘eating’ the lunches of those less good at using software, software embedded in everything or designing everything (and anything else being obsolete), regulating and mediating every sort of arrangement — with lots of plausible variation as to how this happens.

Now the doubt: does future-motivated interest in software freedom share more with interest in science fiction (i.e., moralistic fantasy) or with interest in future studies and the many parts of various social sciences that aim to improve systems going forward in addition to understanding current and past ones? If the latter, why is software freedom ignored by all of these fields? Possibly most people who do think software is becoming very important are not convinced that software freedom is an important dimension to consider. If so (I would love to see some kind of a review on the matter) it would be most reasonable to follow the academic consensus (even if it is one of omission; that consensus being of software freedom not interesting or important enough to investigate) and if one cares about the ethical dimensions of software, focus instead on the ones the consensus says are important.

Two additional posts last year in which I claim software freedom is of outsized and underappreciated importance (of course I don’t usually restrict myself to only software, but consider software a large and growing part of knowledge embodying cumulative innovation, and of the knowledge economy leading to more such accumulation) and some of many from years past (2006, 2006, 2007, 2007). The first from 2006 highlights the most obvious problem with the future. I had forgotten about that post when mentioning displacement of movies by some other form as the height of culture in 2013 — one has to squint to see such displacement even beginning yet. The second isn’t about the future but is closely related: alternative history.

Uncritical Cheering

I feared that many of my posts last year were uncritical cheering (see critical cheering above and last year). Looking back at posts where I’m promoting something, I have usually included or at least hinted at some amount of criticism (e.g., 1 2). I don’t feel too bad. But know that most of the things I promote on my blog are very likely to fail or otherwise be inconsequential — if they were sufficiently mainstream and established they’d be sufficiently covered elsewhere, and I likely wouldn’t bother blogging about them.

One followup: I cheered the publication of the first formally peer-reviewed and edited Wikipedia article in Open Medicine — a journal which has since ceased publishing.

Freeway 980

I continue to blog about removing freeway 980, which cuts through the oldest parts of Oakland. Doubt: I don’t know whether full removal would be better (at least when considering feasibility) than capping the portion of 980 which is below grade. I intended to read about freeway capping, come to some informed opinion, and blog about it. I have not, but supposedly Oakland mayor Libby Schaaf has mentioned removing 980. Hopefully that will spur much more qualified people to publish analyses of various options for my reading pleasure. ConnectOakland is a website dedicated to one removal/fill scenario.

Politics

I’m satisfied enough with the doubt in my two posts about Mozilla’s leadership debacle, but I’ll note apparent tension between fostering ideological diversity and shunning people who would deny some people basic freedoms. I don’t think this one was fairly clear cut, but there are doubtless far more difficult cases in the world.

Instead of doubt, I’d like to clarify my intention with two other posts: thought experiment/provocation, serious demand.

Refutation

I fell further behind, producing no new dedicated collections of refutations of my 8+ year old posts. My very next post will be one, but as with previous such posts, the refutations will be cheap — flippant rather than drilling down on doubts I may have gained over the years. Again these observations (late, cheap) are what led me last year to initiate a thematic doubt post covering the immediately previous year. How was this one?

What is the attribution revolution?

Tuesday, February 3rd, 2015

Elog.io suggested tweet:

I believe in giving and receiving credit for photographs online. Do you? Join the #attributionrevolution – http://elog.io/40m/

Down with the romance of authorship and the ideas that credit is due (as suggested at the link) and that information propertization and the legal system are appropriate mechanisms for encouraging credit (as suggested by licenses mentioned in the campaign which condition free speech on providing attribution).

But I support elog.io despite a bit of ugly rhetoric in its messaging because the technology is fundamentally about making provenance available on demand — undermining the rationale for consciously giving credit or making lack of explicit credit a cause for legal action.

The real attribution revolution has nothing to do with believing that credit is due anyone, and everything to do with attribution (in multiple senses, but including work-creator relationship identification) becoming inescapable, at least not without great and very careful effort. Elog.io is the tip of the top of the iceberg of image and other huge databases (in a sense literally: elog.io apparently is an open database, while others millions of times larger are opaque, submerged beneath corporate and government seawater) and techniques like deep learning and stylometry make universal attribution not only feasible but seemingly inevitable. I don’t know whether this is on net a good or bad thing — but it is the real attribution revolution.

14 months ago I railed against the attribution condition of some open and semi-open licenses (emphasis added):

Do not take part in the debasement of attribution, and more broadly, provenance, already useful to readers, communities of practice, and publishers, by making them seem mere objects of copyright license compliance. If attribution is useful, it will be provided. If not, robots will find out. Rarely does anyone comply with the exact legal requirements of the attribution term anyway, and as a licensor, you probably won’t provide the information needed by licensees to easily comply. Plus, the corresponding icon looks like a men’s bathroom sign.

The elog.io campaign page for example: it does not “include a copy of, or the Uniform Resource Identifier (URI) for, this License with every copy of the Work You Distribute or Publicly Perform” nor does it provide “the URI, if any, that Licensor specifies to be associated with the Work, unless such URI does not refer to the copyright notice or licensing information for the Work” — in other words, it names the works it uses and the licenses it uses them under, but does not link to those works and licenses (quotes from CC-BY-3.0).

The other reason I support elog.io (yes visit that campaign page, give, and ignore the utter triviality of attribution license non-compliance) is that it is focused on provenance for open works (freely licensed or in the public domain — with caveat that I haven’t checked whether it includes semi-open works) and is itself an open source/open data project — provenance for the commons, and commons for the provenance.

Much more work in this area is needed, especially with a focus on high value open works (e.g. premium video) and creating high value open works — I mean by creating network effects around open works, not creating the works themselves. But even a still image focused project could help a bit — every frame of every open premium video could be included in the database, and any use metrics that can be extracted can be used to document and thus abet popularity.

Libre Graphics World has a long interview with elog.io founder Jonas ?berg that is well worth reading. Separately, there is big news not about but very pertinent to elog.io (which also perhaps explains why the elog.io campaign is only attempting to raise $6,000): ?berg is returning to work at the Free Software Foundation Europe (of which he is a co-founder and will be executive director; I had the pleasure of working with him a bit in between at Creative Commons, where he was European coordinator).

I don’t know the FSFE that well, but my impression is very positive, in particular its engagement in politics as public policy, not only the petite politics of individual developers choosing particular licenses and individual users rejecting proprietary software. Congratulations to Jonas on both the elog.io campaign and the FSFE position, and hoping for great success in both. Especially the latter could have an important role in making the real attribution revolution relatively beneficent.

Happy GNU Year & Public Domains Day

Thursday, January 1st, 2015

This Public Domain Day I recommend watching a 2005 lecture or corresponding 2006 journal article Enriching Discourse on Public Domains (summary) by Pamela Samuleson.

The video was only published by Duke Law (which also hosts the main U.S.-centric public domain day page) to their YouTube channel a month ago. Based on the first version (2013-01-02) of my attempted summary, I read the paper the day after my public domain day post 2 years ago, Public Domains Day, which riffed on dictionary definitions.

Samuelson outlines 13 meanings found in law review articles (see the summary for a quick listing) and points out some benefits and one cost of accepting multiple definitions:

+ avoid disputes about “the” correct or one true definition
+ broadened awareness of public domains and public domain values
+ facilitation of context-sensitive discussion
+ enable nuanced answers to questions about various public domains (eg shrinking or not?)
+ possibility of gaining insight into public domain values through consideration of different public domains (deemed most important by author)
– possible confusion concerning what a communicator means by “public domain”

In the lecture Samuelson says it took a long time for her to accept multiple definitions, in part after realizing that other fields such as property law successfully use multiple context-dependent definitions. I’d like to add a plus to the list:

+ language is fun, play with it!

Hectoring people for not using the deemed-by-you to be the one true definitions of the correct words is the opposite of fun. I do tend to use nonstandard words and phrases such as “copyrestriction”, “inequality promotion”, “intellectual freedom infringement”, “intellectual parasite”, and “intellectual protectionism” in order to make a point and have fun, but have descended to hectoring at times (and probably have been perceived as having done so more). I will from now make more of an effort to use terms other people use, or when not, give a fun and non-hectoring rationale. In the meantime, I will say that though I agree with many individual points made concerning word avoidance, I find such neither fun nor welcoming nor helpful in convincing anyone that freedom and equality need to be the dominant objectives of information policy.

At the beginning of the lecture Samuelson is given an introduction lauding her work, initially lonely but presented in 2005 as central, toward making intellectual property scholarship discourse consider the value of the various public domains and costs of expanding (scope, duration, protections) intellectual property rights. I have long been a fan of Samuelson’s work, but the introduction served to remind me of how unsatisfied I am with what still constitutes the liberalizing reform (which itself is possibly central, but I am too ignorant of the breadth of IP scholarship, which surely includes much so-called “maximalism”, to say) line:

  • acknowledgement that we can say little about the net benefits of IP
  • but it is surely “unbalanced” toward protection now
  • so it needs balancing and tuning
  • but of course IP is crucial so genuflect to drugs and movies
  • (largely through omission) commons are a band-aid and not central to reform
  • (largely through omission) freedom and equality not the central objectives

Of course not, as then we would have commons scholarship, not IP scholarship. I contend that pro-commons policy and products are the most feasible, sustainable, and overall best reforms and that freedom and equality should be the dominant objectives — I want the innovations and entertainment produced by a freedom respecting regime — surely meaning substantially less monopoly, hopefully a bit less embarrassing spectacle.

Image from last year, with ‘s’ added to ‘domain’; I’ve written enough recently about ‘GNU’ (signifying software freedom, not the GNU project strictly speaking).

Happy GNU Year & Public Domain Days

wikidata4research4all

Sunday, December 21st, 2014

Recently I’ve uncritically cheered for Wikidata as “rapidly fulfilling” hopes to “turn the universal encyclopedia into the universal database while simultaneously improving the quality of the encyclopedia.” In April I uncritically cheered for Daniel Mietchen’s open proposal for research on opening research proposals.

Let’s combine the two: an open proposal for work toward establishing Wikidata (including its community, data, ontologies, practices, software, and external tools) as a “collaborative hub around research data” responding to a European Commission call on e-infrastructures. That would be Wikidata for Research (WD4R), instigated by Mietchen, who has already assembled an impressive set of partner institutions and an outline of work packages. The proposal is being drafted in public (you can help) and will be submitted January 14.

4all

The proposal will be strong on its own merits, and very well aligned with the stated desired outcomes from the EC call, and the open proposal dogfood angle is also great. I added for all to this post’s title because I suspect WD4R will be a great for pushing Wikidata toward realizing aforementioned “universal database” hopes (which again means not just the data, but community, tools, etc.; “virtual research environment” is one catch-all term) and will make Wikidata much more useful “research” most broadly construed (e.g., by students, journalists, knowledge workers, anyone), potentially much faster than would happen otherwise.

My suspicion has two bases (please correct me if I’m wrong about either):

  1. A database or virtual environment “for research” might give the impression of someplace to dump data from or perform experiments. Maybe that would be appropriate for Wikidata in some instance, but the overwhelming research-supporting use would seem to be mass collaboration in consolidating, annotating, and correcting data and ontologies which many researchers (and researchers-broadly-construed, everyone) can benefit from, either querying or referencing directly, or extracting and using elsewhere. The pre-existing Gene Wiki project which is beginning to use Wikidata is an example of such useful-to-all collections (as referenced in the WD4R pages).
  2. One of the proposed work packages is to identify and work on features needed for research but not on, or not prioritized on, the Wikidata development plan. I suspect other Wikimedia projects can tremendously benefit from Wikidata integration without Wikidata itself or external tools supporting complex queries and reporting that would be called for by a virtual research environment — and also called for to realize “universal database” hopes. Wikidata’s existing plan looks good to me; here I’m just saying WD4R might help it be even better, faster.

The previously linked Gene Wiki post includes:

For more than a decade many different groups have proposed and many have implemented solutions to this challenge using standards and techniques from the Semantic Web. Yet, today, the vast majority of biological data is still accessed from individual databases such as Entrez Gene that make no attempt to use any component of the Semantic Web or to otherwise participate in the Linked Open Data movement. With a few notable exceptions, the data silos have only gotten larger and problems of fragmentation worse.
[…]
Now, we are working to see if Wikidata can be the bridge between the open community-driven power of Wikipedia and the structured world of semantic data integration. Can the presence of that edit button on a centralized knowledge base associated with Wikipedia help the semantic web break through into everyday use within our community?

I agree that massive centralized commons-oriented resources are needed for decentralization to progress (link analogous but not the same — linked open data : federation :: data silos : messaging silos).

Check out Mietchen’s latest WD4R blog post and the WD4R project page.

Defensive Patent License 1.1 w/diff

Tuesday, December 9th, 2014

13 months ago I wrote about the Defensive Patent License, in particular in relation to free/open source software (followup, 1993 predecessor). Today the DPL project released DPL 1.1 and announced the first licensor; see Internet Archive and EFF posts.

(The EFF post references its earlier guide to alternative patent licensing which I meant to critique, probably along lines of a partially overalpping guide to reform proposals, see patent reform, parts deficient in commons and compare with protect commons from patents. I noticed today that one of the other alternative licensing schemes, License On Transfer, seems to be getting some uptake.)

Most of what I wrote previously about the DPL concept still applies with DPL 1.1 (interesting concept, possibility of substantial good impact in long term). The new version makes one major improvement (especially in relation to FLOSS) — the exclusion of “clone” products or services from the license grant has been removed. Another small (as in a -3 words difference) improvement is that alleging patent invalidity against another DPL user no longer breaches one’s licenses (only alleging infringement does), invalidation being a defensive tactic.

DPL 1.1 also adds the requirement of explicit acceptance, which strikes me as burdensome: one must research licensed patents in order to figure out which DPL users to contact with acceptance, or regularly contact all known DPL users with acceptance of all licensed patents. I understand from the DPL 1.1 announcement telecon that formal acceptance was added because the license grant is more likely to stand up in court with such explicit acceptance, with that more likely assessment based on differences between patent and copyright, and between clubs and public licenses — and further that the “contact all known DPL users” practice will in the future be facilitated by the DPL website.

Finally, a very minor issue: DPL 1.1 reproduces the GPL’s confusing three-option version compatibility scheme (this-version-or-later, only-this-version, or any-version-if-none-specified). If one must have options, I consider less confusing this-version-or-later as default, with option to explicitly mandate only-this-version.

Congratulations and thanks to Jason Schultz, Jennifer Urban, Brewster Kahle, John Gilmore, and others for getting the DPL into production. I hope it is wildly successful; check out the DPL website and help update the Wikipedia article.

Following is a wdiff between DPL 1.0 and 1.1 in two parts (because 1.0 put definitions at the beginning, 1.1 puts them at the end) below, excluding 1.1’s preface, which has no equivalent in 1.0.

DPL 1.0-1.1 wdiff: Grant, conditions, etc.

[-2.-]{+1.+} License Grant

Subject to the conditions and limitations of this [-License and upon-]
[-affirmative assent to the commitments specified in Section 1.7 from an-]
[-individual DPL User,-] {+License,+} Licensor hereby
grants and agrees to grant to [-such-] {+any+} DPL User {+(as defined in Section 7.6) who+}
{+follows the procedures for License Acceptance (as defined in Section 1.1)+}
a worldwide, royalty-free, no-charge, non-exclusive, irrevocable (except
as stated in Sections [-3(e)-] {+2(e)+} and [-3(f))-] {+2(f))+} license, perpetual for the term of
the relevant Licensed Patents, to make, have made, use, sell, offer for
sale, import, and distribute Licensed Products and Services that would
otherwise infringe any claim of Licensed Patents. A Licensee’s sale
of Licensed Products and Services pursuant to this agreement exhausts
the Licensor’s ability to assert infringement [-by-] {+against+} a downstream
purchaser or user of the Licensed Products or Services.

[-2.1-] {+Licensor’s+}
{+obligation to grant Licenses under this provision ceases upon the arrival+}
{+of any applicable Discontinuation Date, unless that Date is followed by+}
{+a subsequent Offering Announcement.+}
{++}
{+1.1+} License Acceptance

In order to accept this License, Licensee must {+qualify as a DPL User+}
{+(as defined in Section 7.6) and must+} contact Licensor via the
[-contact-] information
provided in [-Section 1.16 and-] {+Licensor’s Offering Announcement to+} state affirmatively that
Licensee accepts the terms of this License. Licensee must also {+communicate+}
{+the URL of its own Offering Announcement (as defined in Section 7.13) and+}
specify whether it is accepting the License to all Licensor’s Patents or
only a subset of those Patents. If Licensee is only accepting the License
to a subset of Licensor’s Patents, Licensee must specify each individual
{+Patent’s country of issuance and corresponding+} patent [-by patent number.-]
[--]
[-3.-] {+number for which+}
{+it is accepting a License. There is no requirement that the Licensor+}
{+respond to the Licensee’s affirmative acceptance of this License.+}
{++}
{+2.+} License Restrictions

Notwithstanding the foregoing, this License is expressly subject to and
limited by the following restrictions:

(a) No Sublicensing. This License does not include the right to sublicense
any Licensed Patent of any Licensor.

(b) License Extends Solely to Licensed Patents in Connection with Licensed
Products and Services. For clarity, this License does not purport to
grant any rights in any Licensor’s copyright, trademark, trade dress,
design, trade secret, other intellectual property, or any other rights of
Licensor other than the rights to Licensed Patents granted in Section 2,
nor does the License cover products or services other than the Licensed
Products and Services.  {+For example, this License would not apply to+}
{+any conduct of a Licensee that occurred prior to accepting this License+}
{+under Section 1.1.+}

(c) Scope. This License does not include Patents with a priority date
or Effective Filing Date later than Licensor’s last Discontinuation
Date that has not been followed by a subsequent Offering Announcement
by Licensor.

(d) Future DPL Users. This License does not extend to any DPL User whose
Offering Announcement occurs later than Licensor’s last Discontinuation
Date that has not been followed by a subsequent Offering Announcement
by Licensor.

(e) Revocation and Termination Rights. Licensor reserves the right to
revoke and/or terminate this License with respect to a particular Licensee [-if:-]
{+if, after the date of the Licensee’s most recent Offering Announcement:+}
{++}
{+i.+} Licensee makes any Infringement Claim, not including Defensive Patent
Claims, against a DPL User; or

{+ii.+} Licensee {+assigns, transfers, or+} grants an exclusive [-license,-]
[-    with the right to sue, or assigns or transfers-] {+license for+}
a Patent to an entity or individual other than a DPL User without
conditioning the [-transfer-] {+assignment, transfer, or exclusive license+} on the [-transferee-]
{+recipient+} continuing to abide by the terms of this [-License.-] {+License, including but+}
{+not limited to the revocation and termination rights under this Section.+}

(f) Optional Conversion to FRAND Upon Discontinuation. [-As-] {+Notwithstanding+}
{+any other provision in this License, as+} of any particular Licensee’s
Discontinuation Date, Licensor has the right to convert the License of
that particular Licensee from one that is royalty-free and no-charge to
one that is subject to Fair, Reasonable, And Non-Discriminatory (FRAND) [-terms.-]
[--]
[-4.-]
{+terms going forward. No other terms in the license may be altered in+}
{+any way under this provision.+}
{++}
{+3.+}        Versions of the License

[-4.1-]

{+(a)+} New Versions

The DPL [-Foundation is-] {+Foundation, Jason M. Schultz of New York University, and Jennifer+}
{+M. Urban of the University of California at Berkeley are+} the license [-steward. No-]
{+stewards. Unless otherwise designated by one of the license stewards,+}
{+no+} one other than the license [-steward-] {+stewards+} has the right to modify or publish
new versions of this License. Each version will be given a distinguishing
version number.

[-4.2-]

{+(b)+} Effect of New {+or Revised+} Versions

[-Licensed Products and Services-]

{+Any one of the license stewards+} may {+publish revised and/or new versions+}
{+of the DPL from time to time. Such new versions will+} be [-used, made, sold, offered for sale,-]
[-imported, or distributed under-] {+similar in spirit+}
{+to+} the [-terms-] {+present version, but may differ in detail to address new problems+}
{+or concerns.+}
{++}
{+Each version is given a distinguishing version number. If Licensor+}
{+specifies in her Offering Announcement that she is offering a certain+}
{+numbered version+} of the [-version-] {+DPL “or any later version”, Licensee+}
{+has the option+} of {+following+} the [-License-]
[-originally accepted pursuant to Section 2.1,-] {+terms and conditions either of that+}
{+numbered version+} or [-under-] {+of any later version published by one of+} the [-terms-] {+license+}
{+stewards. If Licensor does not specify a version number+} of {+the DPL in+}
{+her Offering Announcement, Licensee may choose+} any
[-subsequent-] version {+ever+} published
by {+any of+} the license [-steward.-]
[--]
[-5.-] {+stewards.+}
{++}
{+4.+}        Disclaimer of Claims Related to Patent Validity and [-Noninfringement.-]
{+Noninfringement+}

Licensor makes no representations and disclaims any and all warranties
as to the validity of the Licensed Patents or [-that-] {+the+} products or processes
covered by Licensed Patents do not infringe the patent, copyright,
trademark, trade secret, or other intellectual property rights of any
other party.

[-6.-]

{+5.+}        Disclaimer of [-Warranties.-] {+Warranties+}

UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING,
LICENSOR OFFERS THE PATENT LICENSE GRANTED HEREIN “AS IS” AND
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE
LICENSED PATENTS OR ANY PRODUCT EMBODYING ANY LICENSED PATENT, EXPRESS
OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION,
WARRANTIES OF TITLE, [-MERCHANTIBILITY,-] {+MERCHANTABILITY,+} FITNESS FOR A PARTICULAR PURPOSE,
NONINFRINGEMENT, OR THE PRESENCE OR ABSENCE OF ERRORS, REGARDLESS OF THEIR
DISCOVERABILITY. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED
WARRANTIES, IN WHICH CASE SUCH EXCLUSION MAY NOT APPLY TO LICENSEE.

[-7.-]

{+6.+}        Limitation of [-Liability.-] {+Liability+}

LICENSOR SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING FROM OR RELATED TO
THIS LICENSE, INCLUDING INDIRECT, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR
SPECIAL DAMAGES, WHETHER ON WARRANTY, CONTRACT, NEGLIGENCE, OR OTHERWISE,
EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES
PRIOR TO SUCH AN OCCURRENCE.

DPL 1.0-1.1 wdiff: Definitions

[-1.-]{+7.+} Definitions

[-1.1-]

{+7.1+} “Affiliate” means a corporation, partnership, or other entity in
which the Licensor or Licensee possesses more than fifty percent (50%) of
the ownership interest, representing the right to make the decisions for
such corporation, partnership or other entity which is now or hereafter,
owned or controlled, directly or indirectly, by Licensor or Licensee.

[-1.2  “Clone Products or Services” means products or services of-]
[-Licensee that include the same or substantially identical functionality of-]
[-all or a commercially substantial portion of a prior released product or-]
[-service of a Licensor and implement the same or a substantially identical-]
[-proprietary user interface of the prior product or service.-]
[--]
[-1.3-]

{+7.2+} “Defensive Patent Claim” means an Infringement Claim against a
DPL User made in response to a pending prior Infringement Claim by said
DPL User against the asserter of the Defensive Patent Claim.

[-1.4-]

{+7.3+} “Discontinuation Announcement” means a DPL User’s announcement
that:

{+(a)+} declares the DPL User’s intent to discontinue offering to license
its Licensed Patents under the DPL, effective as of the Discontinuation
Date; and

{+(b)+} contains the DPL [-User's-] {+User’s+} contact information for licensing purposes;
and [-is submitted to the DPL-]
[-    Website via the Websites's official email address-]

{+(c)+} at least 180 days prior to [-a-] {+the+} Discontinuation [-Date;-] {+Date is posted to a+}
{+publicly accessible website;+} and

{+(d)+} at least 180 days prior to the Discontinuation Date is [-posted to a publicly accessible-]
[-    indexed-] {+communicated+}
{+reasonably and promptly, along with the URL of the+} website [-controlled-] {+mentioned in+}
{+subsection (c) of this provision,+} by the {+discontinuing+} DPL User [-using a URL accessible-]
[-    via at least the following syntax: "http://www.NAME.com/DPL" or-]
[-    "http://www.NAME.com/defensivepatentlicense" where "NAME" is-] {+to every+}
{+Licensor of+} a [-name-]
[-    commonly associated with-] {+Patent to which+} the {+discontinuing+} DPL [-user, such as-] {+User is+} a [-company name.-]
[--]
[-1.5-] {+Licensee.+}
{++}
{+7.4+} “Discontinuation Date” means the date a DPL User specifies in
[-their-]
{+its+} Discontinuation Announcement to discontinue offering to license its
Licensed Patents under the DPL, which must be at least 180 days after
the date of an individual or entity’s most recent Discontinuation
Announcement.

[-1.6-]

{+7.5+} “DPL” and “License” mean the grant, conditions, and
limitations herein.

[-1.7-]

{+7.6+} “DPL User” means an entity or individual that:

{+(a)+} has committed to offer a license to each of its Patents under the [-DPL, or, if such entity or individual has no Patents, has-]
[-    committed to offer a license to any Patents it may obtain in the-]
[-    future under the-]
DPL; and

{+(b)+} has declared such commitment by means of an Offering Announcement; and

{+(c)+} if the entity or individual has made a Discontinuation Announcement,
the Discontinuation Date has not yet occurred; and

{+(d)+} has not engaged in the conduct described in either Sections [-3(e)(i)-] {+2(e)(i)+}
or [-3(e)(ii).-]
[--]
[-1.8 “DPL Website” means the website-]
[-at http://www.defensivepatentlicense.org,-]
[-http://www.defensivepatentlicense.com, or any future site designated by-]
[-the DPL Foundation.-]
[--]
[-1.9-] {+2(e)(ii).+}
{++}
{+7.7+} “Effective Filing Date” is the effective filing date determined
by the applicable patent office that issued the relevant Licensed Patent.

[-1.10 “Foundry Services or Products” means services provided by-]
[-Licensee to, or products manufactured by Licensee for or on behalf of,-]
[-a specific third party, using designs or specifications received in-]
[-a substantially completed form from that third party, for resale or-]
[-relicense to or on behalf of that third party. This definition will not-]
[-apply when:-]
[--]
[-    Licensee or its Affiliate owns the design or specification of such-]
[-    service or product and the service or product is not specifically-]
[-    designed for commercial exploitation substantially only by such third-]
[-    party; or such design or specification resulted from a bona fide joint-]
[-    development or joint participation between Licensee or its Affiliate-]
[-    and such third party, including but not limited to a standards body-]
[-    or community organization and the resulting products, services or-]
[-    components provided by Licensee or its Affiliate meet the definition-]
[-    of Licensed Services Product or Products as set forth herein; or-]
[-    the third party recipient of the products or services is a DPL User.-]
[--]
[-1.11-]

{+7.8+} “Infringement Claim” means any legal action, proceeding or
procedure for the resolution of a controversy in any jurisdiction in
the world, whether created by a claim, counterclaim, or cross-claim,
alleging patent [-infringement or patent invalidity.-] {+infringement.+} Such actions, proceedings, or procedures
shall include, but not be limited to, lawsuits brought in state or
federal court, binding arbitrations, and administrative actions such as
a proceeding before the International Trade Commission.

[-1.12-]

 {+7.9+} “Licensed Patents” means any and all Patents (a) owned or
 controlled by Licensor; or (b) under which Licensor has the right
 to grant licenses without the consent of or payment to a third party
 (other than an employee inventor).

[-1.13-]

{+7.10+} “Licensed Products and Services” means any products, services
or other activities of a Licensee that practice one or more claims of
one or more Licensed Patents of a [-Licensor, but excluding Foundry Services-]
[-or Products and Clone Products or Services.-]
[--]
[-1.14-] {+Licensor.+}
{++}
{+7.11+} “Licensee” means any individual, corporation, partnership or
other entity exercising rights granted by the Licensor under this License
including all Affiliates of such entity.

[-1.15-]

{+7.12+} “Licensor” means any individual, corporation, partnership or
other entity with the right to grant licenses in Licensed Patents under
this License, including any Affiliates of such entity.

[-1.16-]

 {+7.13+} “Offering Announcement” means a Licensor’s announcement that:

{+(a)+} declares the Licensor’s commitment to offer a [-license to-] {+Defensive Patent+}
{+License for any of+} its Patents
    [-under the DPL, or, if such Licensor has no Patents, the commitment to-]
[-    offer a license-] to any [-Patents it may obtain in the future under the-]
[-    DPL;-] {+DPL User;+} and

{+(b)+} contains the Licensor’s contact information for licensing purposes;
and [-is submitted to the DPL Website via the Website’s-]
[-    official email address; and-]

{+(c)+} is posted to a publicly accessible
    [-indexed website controlled by Licensor using a URL accessible-]
[-    via at least-] {+website.+}
{++}
{+An Offering Announcement may, but is not required to, specify the+}
{+particular version of the DPL that+} the [-following syntax: "http://www.NAME.com/DPL" or-]
[-    "http://www.NAME.com/defensivepatentlicense" where "NAME"-] {+Licensor+} is {+committed to+}
{+offering. It may also specify+} a [-name-]
[-    commonly associated with Licensor, such as a company name.-]
[--]
[-1.17-] {+particular version of the DPL “or any+}
{+later version” to allow Licensees to accept subsequent new or revised+}
{+versions of the DPL.+}
{++}
{+7.14+} “Patent” means any right, whether now or later acquired,
under any national or international patent law issued by a governmental
body authorized to issue such rights. For clarity, this definition
includes any rights that may arise in patent applications, utility
models, granted patents, including, but not limited to, continuations,
continuations-in-part, divisionals, provisionals, results of any patent
reexaminations, and reissues, but excluding design patents or design
registrations.

Friends of Software Freedom, Conservationists, Rangers: Support!

Wednesday, December 3rd, 2014

Software Freedom Conservancy, a nonprofit I serve on the board of, today announced a supporter program.

There’s plenty of info at the previous links, so I’ll just add four notes:

  1. Since Karen Sandler started as executive director earlier this year, Conservancy has been doing especially great work for its member projects (and some exciting new ones will be coming on board in the next months; if you lead a free software project, look at info on becoming a member) and is becoming even more the thought leader in both reactionary and progressive (I’m not using those terms to mark ideology here) strategies for software freedom (the italicized modifiers are there because Conservancy was already doing great work, and Sandler had been involved from the very beginning has a volunteer).
  2. Conservancy’s free software non-profit accounting project did not meet its funding goal last year, so progress this year has been slow. It’s still an important project and a successful supporters program will help free up and add resources to move it forward.
  3. Because this is the time of year end appeals (I’ll probably mention a few others in passing shortly), it’s worth noting that Bradley Kuhn (Conservancy’s president and distinguished technologist, but this is one of his many volunteer efforts) is the primary maintainer of a repository of tax filings and other data for free/open organizations. Most of this information can be found somewhere on the web, but not conveniently. Patches welcome (I’d enjoy a dedicated website, and worldwide coverage). Conservancy itself has a page with its filings and a couple explanatory posts.
  4. Didn’t I just a few days ago promote a sort of meta service for free/libre/open projects, Snowdrift.coop? Yes, but it and Conservancy are rather different on multiple dimensions. Snowdrift.coop is a crazy speculative crowdfunding platform. Conservancy is a fiscal sponsor (plus), an old and well understood model that emphasizes administration and stewardship rather than (confusingly to many people, given “fiscal” and “sponsor”) fundraising. Conservancy is able to process donations for member projects (taking a very reasonable 10% cut). If Snowdrift.coop were to become a well-established mechanism for collecting donations to free/libre/open projects such that Conservancy member projects demanded to use the Snowdrift.coop mechanism, I imagine it would be natural for Conservancy to process such funds for its projects. But, this is speculative.

Christopher Allan Webber also says that donating to Conservancy is a real bang for your buck.