The Tricky Business of “Copylefting” Hardware

Republished from Christian Siefkes:

(the original article, also available in German contains an appendix and many links; this article, though not a new one, is still being circulated and recommended; updated insights would be very welcome)

“It’s probably safe to say that the copyleft principle has been essential for the success of free software. Copyleft means that all versions of a software or document will remain free, preventing companies from creating “value-added” versions of free programs and selling them as proprietary, non-free software. The GNU General Public License (GPL)—the first and most well-known incorporation of the copyleft principle—is used for about 50–70% of all free programs, making it more popular than all other free software licenses together.

At first sight, the situation in the newly emerging field of free and open hardware might seem similar—here, copyleft licenses such as the GPL and the Creative Commons Attribution-ShareAlike License (BY-SA) are very popular too (see below for a more detailed analysis). But actually, the situation is very different for hardware design, since copyleft relies on copyright, and hardware is (in most cases) not protected by copyright law.

* The Problem: Copyleft Depends on Copyright

In hardware design, the copyleft clauses of the GPL and the CC BY-SA license thus don’t work in the way you might expect them to work. Anybody who modifies and spreads the design description is bound by them, but people and companies using the design to build and distribute actual hardware are not. Vendors can modify the hardware and sell or distribute the modified hardware without having to publish their modified design, since licenses only govern the design descriptions (the instructions on how to build the hardware), not the hardware itself.

Here’s how the FSF puts it in their GPL FAQ:

Can I use the GPL to license hardware?

Any material that can be copyrighted can be licensed under the GPL. GPLv3 can also be used to license materials covered by other copyright-like laws, such as semiconductor masks. So, as an example, you can release a drawing of a hardware design under the GPL. However, if someone used that information to create physical hardware, they would have no license obligations when distributing or selling that device: it falls outside the scope of copyright and thus the GPL itself.

The problem is that copyright governs only the distribution of information, but not its usage. If somebody has access to information, they can use them and act upon them in any way they like without violating copyright law.

If a bookseller publishes a book describing how to build a product X, the bookseller cannot prevent me from using this information to build and sell X. The book is protected by copyright laws, but the factual information contained in it is not, and my use of that factual information falls outside of copyright laws. The GPL relaxes the restrictions of copyright, giving me more freedom to use copyrighted information than I would usually have, but of course it cannot deny me the freedoms which I always have, even with full copyright in force.

* A Solution: Patents?

I know of only one license that is specifically targeted at open hardware and tries to work around this issue by relying not only on copyright, but also on a mutual patent immunity clause: the TAPR Open Hardware License, published in May 2007 (Version 1.0). The idea is that the licensor grants everybody who complies with the terms of the license the right to use any relevant patents they control. So if you don’t comply (e.g. by not publishing the “source” for physical products you build based on the licensed information), you might get sued by the licensor for patent violation, but if you comply you’re safe.

TAPR has published two versions of the license: the Open Hardware License (OHL), which emulates standard copyleft (like the GPL or CC BY-SA), and the TAPR Noncommercial Hardware License (NCL), which additionally prohibits commercial usage (like the CC BY-NC-SA).

Relying on patent law instead of copyright law for hardware makes sense, since patent law is made for hardware, while copyright law is made for information. But it’s also a problem, since getting a patent is a difficult and costly process, while getting copyright is free and automatic.

The TAPR licenses will only be really effective if the licensor possesses relevant patents, or at least if people can’t be entirely sure that (s)he doesn’t have any such patents. That’s a pretty bad limitation, since patents are difficult and expensive to get. Most peer projects will be unable or unwilling to apply for a patent, so the TAPR licenses will hardly be suitable for them.

Another unrelated problem of the TAPR licenses is that they require you to distribute the original designs you’ve received from others in addition to your own modified version—you must distribute both “before” and “after” versions of any files you’ve modified (§ 4.2 (b)). This might be extremely impractical for large version histories (think of hundreds or thousands of versions), and it makes the creation of printed versions of modified hardware documentation practically impossible. It’s also unclear what’s the point of this requirement.

* Pragmatic Solutions: Just Use Standard Copyleft — Or No Copyleft Altogether

Most open hardware projects seem to care little about the specific issues of hardware licensing. Most projects aiming for copyleft just apply a standard license such as the GNU GPL or the Creative Commons BY-SA license, apparently either not knowing or not caring that is won’t apply to building hardware (see list of projects below).

Another solution is to forgo copyleft altogether and just use a permissive license such as the (modified) BSD license. This allows everybody to use the provided information in any way they like, without having to keep modifications or improvements open.

There even is a hardware-specific non-copyleft license, the Balloon Licence. The Balloon Licence is a simple MIT-style license. Since it does not try to apply any restrictions on the manufacturing of hardware (no copyleft or non-commercial clause), it doesn’t have the problems of other open hardware licenses. However, since this license is very similar to the commonly used MIT and (modified) BSD licenses and doesn’t address any new issues, there seems to be little reason to choose this special license instead of one of the standard ones.

* What To Do?

As can be seen from the list below, there is a clear tendency of projects to use standard copyleft (the GPL or the CC BY-SA), protecting the design information itself but not any physical hardware built on their basis. Does this mean that projects are willing to live with a limited copyleft, or are they just unaware of the problem? I’m not so sure…

In any case, no convincing solutions seem to exist. The TAPR license, the only license that tries the address the problem of extending copyleft to the hardware itself, never became very popular—almost nobody outside the TAPR project seems to be using it. And indeed, its reliance on patent law makes the license very impractical to use for all but the biggest projects.

On the other hand, just using permissive licenses (like the Apache project and the BSD family do) doesn’t seem to be an attractive option for the majority of open hardware projects—most prefer to get at least the partial copyleft protection that standard licenses such as the GPL and CC BY-SA can give them.

But, as described above, their copyleft protection is very incomplete in case of hardware—hardware builders aren’t required to give back their improvements. In the case of the RONJA project, this difference between hardware builders not giving back but the project maintainers expecting them to do so, has already caused tensions that contributed to the downfall of the project. Whether similar problems will appear in other projects and weaken the open hardware community, remains to be seen … “