Pushing back against licensing and the permission culture
tl;dr: the open license ecosystem assumes that sharing can’t (or even shouldn’t) happen without explicit permission in the form of licenses. What if “post open source” is an implicit critique of that assumption – saying, in essence, “I reject the permission culture”? If so, license authors might want to consider creating options that enable people to express that opinion.
A few months back, James Governor said:
younger devs today are about POSS – Post open source software. fuck the license and governance, just commit to github.
— James Governor (@monkchips) September 17, 2012
While the actual extent of “POSS” is debatable, there is definitely an increase in the amount of unlicensed code out there. This post suggests 20+% of the most-watched github projects are unlicensed. The pushback against licensing isn’t specific to software, either – at least some sharing musicians are deliberately spurning Creative Commons (via Lucas) and Nina Paley has been obliquely making the same point about the licensing of her art as well.
A few months back, I pointed out that the lack of licensing led to confusion and so was great for lawyers. That post was accurate, but slightly glib. Here, I want to grapple more seriously with the rejection of licensing, and provoke the licensing community to think about what that means.
A dab of history and context
In the US, prior to the 1976 Copyright Act, you had to take affirmative steps to get a protectable copyright. In other words, you could publish something and expect others to be able to legally reuse it, without slapping a license on it first.
Since the 1976 Act, you get copyright simply by creating the work in question. That means every blog post and every github commit is copyrighted. This restrictive default, combined with the weakness of fair use, leads to the “permission culture” – the pernicious assumption that you must always ask permission before doing anything with anyone’s work, because nothing is ever simply shared or legally usable. (This assumption is incorrect, but the cost of acting that way can be high if you make a mistake.)
“POSS” might be more than just bad hygiene
It is easy to assume that the pushback against licenses (“post-open source”) is because licensing is confusing/time-consuming and people are lazy/busy. While I’m sure these are the primary reasons, I think that, for some people, the pushback against licenses often reflects a belief that “no copyright should mean no permission needed”. In other words, those people choose not to use a license because, on some level, they reject the permission culture and want to go back to the pre-1976 defaults. In this case, publishing without a license is in some way a political statement – “not every use should need permission”.1
Fixing(?) the politics of our licenses
If some “no license” sharing is a quiet rejection of the permission culture, the lawyer’s solution (make everyone use a license, for their own good!) starts to look bad. This is because once an author has used a standard license, their immediate interests are protected – but the political content of not choosing a license is lost. Or to put it another way: if license authors get their wish, and everyone uses a license for all content, then, to the casual observer, it looks like everyone accepts the permission culture. This could make it harder to change that culture – to change the defaults – in the long run.
So how might we preserve the content of the political speech against the permission culture, while also allowing for use in that same, actually-existing permission culture? Or to put it more concisely:
What would a “license” that actively rejects the permission culture look like?
A couple of off-the-wall options:
- Permissive+political preamble license: The WTFPL license (“Do WTF you want“) has been floating around for ages, and using it makes the point that (1) you want people to use your code and (2) you’re irritated that they even have to ask. Adding a brief “I hate that I have to do this” preamble to a permissive license like CC-0 might serve a similar purpose, while providing more legal certainty than WTFPL. (And of course such a preamble could also be used with a strong copyleft, like copyleft-next.)
- Fair Use supplement: Fair use is the traditional safety valve for copyright, but it is hard to know if a particular use is “fair.” So a “license” could be written that, instead of formally licensing under specific terms, instead aims to provide more certainty about fair use. Some ways this could be done would include broadly defining the fair use categories, explicitly accepting transformative use as a factor in the fair use analysis, or asking courts to interpret ambiguity in favor of the recipient instead of the author. It is also possible to imagine this as a supplement to the existing fair use clauses in modern licenses (CC-BY 3.0 Sec. 2, GPL v3 Sec. 2, MPL 2 Sec 2.6), laying out a strong vision of fair use to help guide and protect anyone relying on those clauses.
- “What People Actually Think Copyright Is” license: most Americans2 think that personal use of copyrighted materials is legal under modern copyright law. So a license that focused on personal use might work better than the more nebulous “non-commercial”. As a bonus, since commercial interests will clearly be unable to use the content, getting it “right for lawyers” may be less of a concern.
Careful readers will note that the last two options are unlikely to be OSI-open or FSF-free. For the purposes of this exercise, that’s OK- OSI, FSF, and CC’s iron-clad assumption that licensing is good is what I’d like to provoke people to think about here.3
Conclusion, and provocation
I don’t offer these license ideas as a comprehensive survey of what an anti-permission-culture license might look like, or even a good survey. Instead, take them as a provocation: are we – particularly authors and evaluators of open licenses – part of the problem of the permission culture? Are we actually responding to the people who use our licenses, if one of their desires is to push back against the need to license? Can we be more creative about expressing distaste for the permission culture, without gumming up the works of sharing too much? I think that, if we think critically, we can, and perhaps we should.
- Another motive, that I won’t go into here but which also deserves serious discussion for license authors, is simply that the values encapsulated in our licenses are taken for granted by younger developers who have always had a plentiful, healthy free-as-in-beer code commons. Both the permissive and copyleft communities would do well to argue the case for their licenses (not just their overall philosophies) better than they currently do.
- per Jessica Littman, Digital Copyright, p. 117
- If it wasn’t already obvious, this post is obviously not made with my OSI hat on – OSI continues to firmly endorse the Open Source Definition.