Best Open Source License For Hardware?
An anonymous reader writes "MIT recently open-sourced some really cool hardware designs, including an H.264 video decoder and an OFDM transceiver, under MIT's open source license (a.k.a. the X11 license). Now, the OpenCores FAQ recommends that people use either the GPL, LGPL, or modified BSD license; they do not mention the MIT license at all. And, according to the Free Software Foundation the GPL license can be used for hardware, but they do not list the LPGL, modified BSD, or MIT licenses as suitable for non-software. Would you or your company use hardware source-released under the MIT license? What's the best license to use for releasing hardware?"
Public Domain.
Why? So companies dont mind making it themselves. They profit on it. When other companies make it too, they can do so without reprisal on licenses, so the price approaches cost+"token profit".
Also, by having the circuit schematic public, hiding undesirable plans is pretty much impossible.
Yet, you still have the issue of licensing.
You can hold the sole rights of production, you can charge people for the right to produce more of the thing, you can just let anyone produce more of the thing, or presumably, you can do something in between: offer limited rights to reproduce your invention for free if certain conditions are met, which is precisely the goal of the GPL with respect to software copyright.
Is it so much of a stretch that one or more of the stock "open" software licenses might be suitable with zero or few changes in wording to apply to patent licensing as well?
Can you be Even More Awesome?!
Copyright applies to the expression of an idea, not the idea itself, regardless of whether it's software, hardware, or the great-american-novel.
Hardware designs are most frequently expressed in a hardware-definition language (HDL) such as Verilog or VHDL. The HDL source can be copyrighted just like a program written in your favorite language.
This is the reason that TAPR created the Open Hardware License. It is available in two versions - the Open Hardware License, and the Non-Commercial Open Hardware License. The former is like GPL for hardware, and the latter provides a license that can be used to allow a company to open a design without giving their competitors the chance to use the design commercially.
It is designed to provide many protections including of the circuit designs and layouts, and patent protection.
Darryl
P.S. I am on the board of TAPR
What's the best open-source license to use for biological innovations and strains?
I personally prefer the MPL, the BSD/MIT and lGPL, but would also be interested in seeing what GPL-lovers (those who agree with the FSF's positions) have to say as well.
"The absurd is clear reasoning recognizing its limits"
-Albert Camus
Real hardware is a bit more challenging to release in open source form for many reasons:
* Hardware definitions are done in layout packages with very different file structures etc making it difficult to share designs across diferent tool chains.
* RF and power designs are more physical implementations than schematic ones. That is, it is easy to render a schematic in different physical forms some of which will work and some of which won't.
Engineering is the art of compromise.