Originally posted at eaves.ca
David H. sent me this short and fantastic article from Wired magazine last week.
The article discusses the travails of Mathew Burton, a former analyst and software programmer at the Department of Defense who spent years trying to get the software he wrote into the hands of those who desperately needed it. But alas, no one could figure out the licensing rights for the software it was supposed to work with… so it never went anywhere. Today Mathew has (unsurprisingly) left Defense and has open sourced the code so that anyone can use it. The lesson? The tangled mess of navigating all the license agreements isn’t protecting anyone and certainly not the public. It’s just preventing interesting new and derivative works from being used to render American safer.
In short, the crises here doesn’t have to do with size of government, but in a misplaced desire by many governments to protect “intellectual property.”
Now I understand the need of government to protect physical property. A forest, for example, can only be logged once every few generations, so allocating that resource efficiently matters. But intellectual property? Things like documents, data, and software code? It’s use is not diminished when someone uses it. Indeed, often its value increases when numerous people start to use it.
But rather than give to tax payers the intellectual property their tax dollars already paid for, our governments lock them down. Today, under the false belief that they are protecting themselves and potential revenue streams (that have never materialized) our governments copyright, patent and license all sorts of intellectual property our tax dollars paid for. In short, we treat ideas like we treat forests, something that only a handful of people can use and benefit from.
This has three happy consequences.
First, ideas and innovations are more expensive and spread more slowly. Remember the goal of innovation is not to license technology, its to use technology to enable us to be happier, safer or more productive (or ideally all three!). When our governments license technology that accomplishes one or all of these things they are, in fact, restricting the number of people who can benefit by giving a single actor a monopoly to sell this service (again, one tax payers funded to develop!) to tax payers or (worse) back to the government.
Second, we end up wasting a colossal amount of money on lawyers. With our governments pretending to be a corporation, managing all this intellectual property tax payers funded to develop, we naturally require an army of lawyers to protect and license it!
Finally, many governments are locked out of open source projects and communities. Since, by policy, many governments require that they own any code they, or their contractors develop, they cannot contribute to open source projects (in which the code is by definition, not owned but shared). This means free, scalable and customizable software and products that small companies like Google are forbidden within government. Instead they (and by they, I mean us) have to pay for proprietary solutions.
At some point I’d love to read more about how government got into the intellectual property businesses. I imagine it is a history paved with good intentions. However, the more I reflect on it, the more I wonder why the first order question of “why do governments have intellectual property” never gets asked. The costs are high and the benefits seem quite low. Maybe it’s time we radically rethink this.
It looks like Matthew Burton is a GovLoop member! Perhaps we could entice him to share a bit more thoughts here? 🙂
Here’s what I was able to find related to government and intellectual property…much more concerned about government licensing IP from contractors vs. the other way around:
There are some points that need clarification.
First, there were no intellectual property issues with the government. My decision to open source the code (which isn’t available yet, but will be soon) was based on several reasons, but freeing myself from the grip of government IP was not one of them.
Government action–or, more accurately, inaction–did play a role: though I was developing my tool specifically for a government network built to evaluate potential products like mine, they never provided me technical specifications or terms under which products would be purchased. I sunk a lot of time and money into customizing my code for a platform that was eventually killed. Big contractors can afford to take risks on marketing projects like those, but independent developers cannot.
But again, IP was never an issue here.
Second:
“…many governments require that they own any code they, or their contractors develop, they cannot contribute to open source projects (in which the code is by definition, not owned but shared). This means free, scalable and customizable software and products that small companies like Google are forbidden within government.”
I’m not sure about this. Many government organizations *think* they can’t use open source software, and IANAL, but I don’t believe such a law bars the use of open source. Even copyleft licenses allow you to modify code all you like as long as you don’t redistribute them. If a government agency deployed or modified an open source package for internal use, they’re free to keep those modifications to themselves without ever contributing back to the project. In my experience (restricted mostly to mil and intel), most of the government’s concerns about deploying open source code and contributing back to the project are security-related, not legal. There’s a popular belief among the unsavvy that open source projects are inherently full of security holes (“Anyone off the street can alter this!”), and convincing them otherwise is a big challenge.
I agree with the sentiments about public ownership of taxpayer-funded code, etc.
Hi Matthew,
Thank you for commenting. Good to hear that IP wasn’t a concern in your case.
In reference to the quote:
“…many governments require that they own any code they, or their contractors develop, they cannot contribute to open source projects (in which the code is by definition, not owned but shared). This means free, scalable and customizable software and products that small companies like Google are forbidden within government.”
I can’t speak to all jurisdictions but I know this is a significant issue in Canada. Indeed, many provinces and local governments have policies that explicitly require that any code developed by public servants (or contractors) be owned by the government, precluding the use of the GPL or similar licenses.
Hi everyone. David’s post is hard not to agree with: indeed, it is something of a no-brainer. you could, however, turn the argument on its head and say that the public sector is precisely the place where you do not have to worry about IP, precisely because there is no conflict between the fast adoption but low financial returns of open software (CC or similar licenses) and slow adoption but easy charging of proprietary code, as in the private sector.
A comment on David’s last comment: I am not familiar with GPL, but would not a release in Creative Commons be compatible with Canadian law? You get a contractor, they develop code for you, you release it under CC-By stating “The people of Canada” (or agency XY) as the owner of the rights, voilà! You have a reusable and remixable piece of code that, legally still belongs to the taxpayer.
“Today, under the false belief that they are protecting themselves and potential revenue streams (that have never materialized) our governments copyright, patent and license all sorts of intellectual property our tax dollars paid for. In short, we treat ideas like we treat forests, something that only a handful of people can use and benefit from.”
Actually the original intent (largely evolved during WWII) was precisely the opposite. Corporations were getting huge contracts to develop new technologies and retaining the patent rights for themselves. It seemed unfair for these corporations to profit twice (once from the contract and once from the patent). Also, it was slowing down new development as each corporation negeotiated with others on patents for things like new parachutes, landing craft, armored vehicles etc. so the government started writing patent ownership clauses into the contracts and sharing the patents with other corporations working for the government. The general idea was the public had paid for development of these patents once, so they should not have to pay again when buying products based on them. The concept actually worked fairly well in the defense and space industry during the 40s, 50s and early 60s when DOD and NASA were the major funders of patent development which had little, if any civilian application. The policy began to go off the rails in the late 60s when NASA started owning patents for dual use products (anyone remember TANG?). No one was quite sure how to get these products into the market without giving the intitial contracter an “unfair” advantage. So sometimes agencies just sat on the patents, a few times the ended up in the public domain and occasionally they were sold. Then software came along and everything got completely confused. As one who is old enoug to remeber the bitter debates regarding whether software was in fact intellectual property (Bill Gates was excoriated for his stand on this.) I can sympathise with agency directors and policy makers who have struggeled with how to handle this issue. My own preference would be for the governement to either take ownership of any IP developed for it under contract and put the IP into the public domain or allow the contractor to retain ownership but with a contract clause requiring royalty payments to the government for its use.
Well done, Peter. I find this historical perspective very useful.