Hackerspaces Global Space Program/Legal
Copied from Wikipedia
Rather than creating a new license, some open source hardware projects simply use existing, open source software licenses.
Additionally, several new licenses have been proposed. These licenses are designed to address issues specific to hardware designs. In these licenses, many of the fundamental principles expressed in open source software (OSS) licenses have been "ported" to their counterpart hardware projects. Organizations tend to rally around a shared license. For example, Opencores prefers the LGPL, FreeCores insists on the GPL, Open Hardware Foundation promotes "copyleft" or other permissive licenses", the Open Graphics Project uses a variety of licenses, including the MIT license, GPL, and a proprietary license, and the Balloon Project wrote their own license. New hardware licenses are often explained as the "hardware equivalent" of a well-known OSS license, such as the GPL, LGPL, or BSD license.
Despite superficial similarities to software licenses, most hardware licenses are fundamentally different: by nature, they typically rely more heavily on patent law than on copyright law. Whereas a copyright license may control the distribution of the source code or design documents, a patent license may control the use and manufacturing of the physical device built from the design documents. This distinction is explicitly mentioned in the preamble of the TAPR Open Hardware License.
- "...those who benefit from an OHL design may not bring lawsuits claiming that design infringes their patents or other intellectual property."
- The TAPR Open Hardware License: drafted by attorney John Ackermann, reviewed by OSS community leaders Bruce Perens and Eric S. Raymond, and discussed by hundreds of volunteers in an open community discussion
- Balloon Open Hardware License: used by all projects in the Balloon Project
- Although originally a software license, OpenCores encourages the LGPL
- Hardware Design Public License: written by Graham Seaman, admin. of Opencollector.org
- In March 2011 CERN released the CERN Open Hardware License (OHL) intended for use with the Open Hardware Repository and other projects.
- How to ensure ownership of rights to projects?
- Should projects adhere to a certain set of licenses to be considered eligible? If so, which ones?
<ref> tags exist, but no
<references/> tag was found