Version 1.1 of the definition has been released. Please help updating it, contribute translations, and help us with the design of logos and buttons to identify free cultural works and licenses!

Editing OSHW

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
[[File:Oshw-logo.png|thumb|[[#Logo repository|The Open Source Hardware Logo]]]]
+
== Definition version 0.1==
This page hosts the current proposed Open Source Hardware (OSHW) Statement of Principles and Definition v1.0.  The statement of principles is a high-level overview of the ideals of open-source hardware.  The definition is an attempt to apply those ideals to a standard by which to evaluate licenses for hardware designs.
+
Open-source hardware is that for which its designer:
 +
* provides design files (in the preferred format for making modifications to them)
 +
* allows the modification and redistribution of the design files
 +
* allows the manufacture, sale, distribution, and use of devices from the design files or modifications of the design files
 +
without discrimination against persons, groups, or fields of endeavor.  Additionally, the designer must publish any documentation and release under an open-source license any software it has developed that is essential to the proper functioning of the device.
  
To endorse the Open Source Hardware Definition 1.0, please add your name (and affiliation) [[#Endorsements|below]].
+
The designer may require others to:
 +
* provide attribution when distributing design files based on the original designer's
 +
* provide attribution when manufacturing devices based on the original designer's design files or derivatives thereof
 +
* release as open-source hardware devices based on the original designer's design files or derivatives thereof
  
[[OSHW older drafts|Older drafts of the definition are also available]].
+
Manufacturers of a derivative device must not:
 +
* imply that the device is manufactured, tested, warrantied, guaranteed, or otherwise sanctioned by the original designer
 +
* make use of any trademarks owned by the original designer without explicit permission
  
Compiled community feedback from previous versions of the Definition can be found [http://www.openhardwaresummit.org/compiled-feedback/ here]
+
We recognize that open-source is only one way of sharing information about hardware and encourage and support all forms of openness and collaboration, whether or not they fit this definition.
  
If you would like to propose changes to the statement of principles or definition, please do so on the [[OSHW draft|work-in-progress draft]]. And, please edit while signed in, not anonymously.
+
== Definition version 0.2 (work in progress)==
 +
The designer of open-source hardware will:
  
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]''
+
    * provide design files (in the preferred format for making modifications to them)
 +
    * allow the modification and redistribution of the design files
 +
    * allow the manufacture, sale, distribution, and use of devices from the design files or modifications of the design files
 +
    * publish any documentation and release under an open-source license any software it has developed that is essential to the proper functioning of the device
  
== Open Source Hardware (OSHW) Statement of Principles 1.0 ==
+
without discrimination against persons, groups, or fields of endeavor.  
  
Open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design. The hardware's source, the design from which it is made, is available in the preferred format for making modifications to it.  Ideally, open source hardware uses readily-available components and materials, standard processes, open infrastructure, unrestricted content, and open-source design tools to maximize the ability of individuals to make and use hardware. Open source hardware gives people the freedom to control their technology while sharing knowledge and encouraging commerce through the open exchange of designs.
+
The designer may require others to:
  
== Open Source Hardware (OSHW) Definition 1.0 ==
+
    * provide attribution when distributing design files based on the original designer's
 +
    * provide attribution when manufacturing devices based on the original designer's design files or derivatives thereof
 +
    * release as open-source hardware devices based on the original designer's design files or derivatives thereof
  
''OSHW Draft Definition 1.0 is based on the [http://opensource.org/docs/osd Open Source Definition] for Open Source Software and [http://freedomdefined.org/OSHW_older_drafts draft OSHW definition 0.5]. The definition is derived from the [http://www.opensource.org/docs/osd Open Source Definition], which was created by Bruce Perens and the Debian developers as the Debian Free Software Guidelines. Videos and Documentation of the Opening Hardware workshop which kicked off the below definition are available [http://www.eyebeam.org/projects/Opening-hardware here].''
+
Manufacturers of a derivative device must not:
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]''
 
  
'''Introduction'''
+
    * imply that the device is manufactured, tested, warrantied, guaranteed, or otherwise sanctioned by the original designer
 +
    * make use of any trademarks owned by the original designer without explicit permission
 +
 
 +
Disclaimer:
 +
We recognize that open-source is only one way of sharing information about hardware and encourage and support all forms of openness and collaboration, whether or not they fit this definition.
  
Open Source Hardware (OSHW) is a term for tangible artifacts -- machines, devices, or other physical things -- whose design has been released to the public in such a way that anyone can make, modify, distribute, and use those things. This definition is intended to help provide guidelines for the development and evaluation of licenses for Open Source Hardware.
+
== Definition version 0.3 (work in progress)==
  
Hardware is different from software in that physical resources must always be committed for the creation of physical goods. Accordingly, persons or companies producing items ("products") under an OSHW license have an obligation to make it clear that such products are not manufactured, sold, warrantied, or otherwise sanctioned by the original designer and also not to make use of any trademarks owned by the original designer.
+
''OSHW draft definition 0.3 is based on the [http://opensource.org/docs/osd Open Source Definition] for Open Source Software and [http://freedomdefined.org/OSHW draft OSHW definition 0.2], further incorporating ideas from the [http://www.tapr.org/ohl.html TAPR Open Hardware License].''
  
The distribution terms of Open Source Hardware must comply with the following criteria:
 
  
'''1. Documentation'''
+
'''Introduction'''
  
The hardware must be released with documentation including design files, and must allow modification and distribution of the design files. Where documentation is not furnished with the physical product, there must be a well-publicized means of obtaining this documentation for no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The documentation must include design files in the preferred format for making changes, for example the native file format of a CAD program.  Deliberately obfuscated design files are not allowed.  Intermediate forms analogous to compiled computer code -- such as printer-ready copper artwork from a CAD program -- are not allowed as substitutes.   The license may require that the design files are provided in fully-documented, open format(s).  
+
Open Source Hardware (OSHW), or simply "open hardware," is a term for tangible artifacts-- machines, devices, or other physical things --whose design has been released to the public in such a way that anyone can make, modify, distribute, and use those things. This definition is intended to help provide guidelines for the development and evaluation of licenses for open hardware.
  
'''2Scope'''
+
It is important to note that hardware is different from software in that physical resources must always be committed for the creation of physical goodsAccordingly, persons or companies producing items ("products") under an OSHW license have an obligation not to imply that such products are manufactured, sold, warrantied, or otherwise sanctioned by the original designer and also not to make use of any trademarks owned by the original designer.
  
The documentation for the hardware must clearly specify what portion of the design, if not all, is being released under the license.
+
The distribution terms of open-source hardware must comply with the following criteria:
  
'''3. Necessary Software'''
+
'''1. Documentation'''
  
If the licensed design requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the license may require that one of the following conditions are met:
+
The hardware must be released with documentation including design files, and must allow modification and distribution of the design files.  Where documentation is not furnished with the physical product, there must be a well-publicized means of obtaining this documentation for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The documentation must include design files in the preferred form for which a hardware developer would modify the design. Deliberately obfuscated design files are not allowed. Intermediate forms such as printed artwork from a CAD program are not allowed as substitutes.
  
a)  The interfaces are sufficiently documented such that it could reasonably be considered straightforward to write open source software that allows the device to operate properly and fulfill its essential functions. For example, this may include the use of detailed signal timing diagrams or pseudocode to clearly illustrate the interface in operation.
+
'''2. Necessary Software'''
  
b) The necessary software is released under an [http://www.opensource.org/ OSI]-approved open source license.
+
If the hardware requires software, embedded or otherwise, to operate properly and fulfill its essential functions, then the documentation requirement must also include at least one of the following:  The necessary software, released under an open source license, or other sufficient documentation such that it could reasonably be
 +
considered straightforward to write open source software that allows the
 +
device to operate properly and fulfill its essential functions.
  
'''4. Derived Works'''
+
'''3. Derived Works'''
  
The license shall allow modifications and derived works, and shall allow them to be distributed under the same terms as the license of the original work.  The license shall allow for the manufacture, sale, distribution, and use of products created from the design files, the design files themselves, and derivatives thereof.
+
The license must explicitly allow for the manufacture, sale, distribution, and use of products created from the design files and for the for the manufacture, sale, distribution, of derivative products created from modifications to those design files.  The license must allow these products and derivative works to be distributed under the same terms as the license of the original hardware.
 
   
 
   
'''5. Free redistribution'''
+
'''4. Integrity of The Original Design'''
  
The license shall not restrict any party from selling or giving away the project documentation. The license shall not require a royalty or other fee for such sale. The license shall not require any royalty or fee related to the sale of derived works.
+
The license may restrict design files and other documentation from being distributed in modified form only if the license allows the distribution of "patch files" for the purpose of modifying the design into a derivative work. The license may require derived works to carry a different name or version number from the original design.
  
'''6. Attribution'''
+
'''5. Attribution'''
  
The license may require derived documents, and copyright notices associated with devices, to provide attribution to the licensors when distributing design files, manufactured products, and/or derivatives thereof. The license may require that this information be accessible to the end-user using the device normally, but shall not specify a specific format of display. The license may require derived works to carry a different name or version number from the original design.
+
The license may require derived works to provide attribution to the original designer when distributing design files, manufactured products, and/or derivatives thereof.
  
'''7. No Discrimination Against Persons or Groups'''
+
'''6. No Discrimination Against Persons or Groups'''
  
 
The license must not discriminate against any person or group of persons.
 
The license must not discriminate against any person or group of persons.
  
'''8. No Discrimination Against Fields of Endeavor'''
+
'''7. No Discrimination Against Fields of Endeavor'''
 
 
The license must not restrict anyone from making use of the work (including manufactured hardware) in a specific field of endeavor. For example, it must not restrict the hardware from being used in a business, or from being used in nuclear research.
 
 
 
'''9. Distribution of License'''
 
 
 
The rights granted by the license must apply to all to whom the work is redistributed without the need for execution of an additional license by those parties.
 
 
 
'''10. License Must Not Be Specific to a Product'''
 
 
 
The rights granted by the license must not depend on the licensed work being part of a particular product. If a portion is extracted from a work and used or distributed within the terms of the license, all parties to whom that work is redistributed should have the same rights as those that are granted for the original work.
 
 
 
'''11. License Must Not Restrict Other Hardware or Software'''
 
 
 
The license must not place restrictions on other items that are aggregated with the licensed work but not derivative of it. For example, the license must not insist that all other hardware sold with the licensed item be open source, nor that only open source software be used external to the device.
 
  
'''12. License Must Be Technology-Neutral'''
+
The license must not restrict anyone from making use of the hardware in a specific field of endeavor. For example, it may not restrict the hardware from being used in a business, or from being used in nuclear research.
  
No provision of the license may be predicated on any individual technology, specific part or component, material, or style of interface or use thereof.
+
'''8. Distribution of License'''
  
 +
The rights attached to the hardware must apply to all to whom the product or documentation is redistributed without the need for execution of an additional license by those parties.
  
 +
'''9. License Must Not Be Specific to a Product'''
  
'''Afterword'''
+
The rights attached to the hardware must not depend on the hardware being part of a particular larger product. If the hardware is extracted from that product and used or distributed within the terms of the hardware license, all parties to whom the hardware is redistributed should have the same rights as those that are granted in conjunction with the original distribution.
  
The signatories of this Open Source Hardware definition recognize that the open source movement represents only one way of sharing information. We encourage and support all forms of openness and collaboration, whether or not they fit this definition.
+
'''10. License Must Not Restrict Other Hardware or Software'''
  
== Licenses and Hardware ==
+
The license must not place restrictions on other hardware or software that is distributed along with the licensed hardware. For example, the license must not insist that all other hardware sold at the same time be open source, nor that only open source software be used in conjunction with the hardware.
  
In promoting Open Hardware, it is important to make it clear to designers the extent to which their licenses actually can control their designs. Under U.S. law, and law in many other places, copyright does not apply to electronic designs. [[Patent]]s do. The result is that an Open Hardware license can in general be used to restrict the ''plans'' but ''not'' the manufactured devices or even restatements of the same design that are not textual copies of the original. The applicable section of copyright law is 17.102(b), which says:
+
'''11. License Must Be Technology-Neutral'''
  
:''In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.''
+
No provision of the license may be predicated on any individual technology or style of interface.
  
== Translations ==
+
== Signatories of version 0.1 ==
  
The below translations have been offered by members of the community and should be checked for accuracy and possible language problems.
+
The following people have endorsed this definition of open-source hardware:
 +
* David A. Mellis, MIT Media Lab and Arduino
 +
* Limor Fried, Adafruit Industries
 +
* Phillip Torrone, Adafruit Industries and Senior Editor - MAKE magazine
 +
* Chris Anderson, DIY Drones and Editor in Chief --WIRED Magazine
 +
* Massimo Banzi, Arduino and Tinker it!
 +
* Ken Gilmer, Bug Labs
 +
* Jonathan Kuniholm, Open Prosthetics Project/Shared Design Alliance
 +
* John Wilbanks, Creative Commons
 +
* Zach Smith / Bre Pettis / Adam Mayer, MakerBot Industries
 +
* Nathan Seidle, SparkFun Electronics
 +
* Alicia Gibb, Bug Labs
 +
* Russell Nelson, Open Source Initiative
 +
* David Cuartielles, Arduino and Malmo University
  
{{:OSHW/translations}}
+
== Participants ==
  
== Logo repository ==
+
This definition originated with discussion between attendees of the [http://eyebeam.org/projects/opening-hardware Opening Hardware workshop] at Eyebeam (New York City), March 17, 2010, in particular (listed alphabetically by first name):
  
The open source hardware logo lives at [http://www.oshwa.org/open-source-hardware-logo/ oshwa.org].
+
* Alicia Gibb, Bug Labs
 +
* Ayah Bdeir, Eyebeam
 +
* Benjamin Mako Hill, MIT
 +
* Bunnie Huang, Chumby
 +
* Chris Anderson, Wired Magazine and DIY Drones
 +
* David A. Mellis, MIT Media Lab and Arduino
 +
* Gianluca Martino, Arduino
 +
* John Wilbanks, Creative Commons
 +
* Jonathan Kuniholm, Open Prosthetics Project/Shared Design Alliance
 +
* Ken Gilmer, Bug Labs
 +
* Ken Gracey, Parallax
 +
* Limor Fried, Adafruit Industries
 +
* Massimo Banzi, Arduino
 +
* Nathan Seidle, SparkFun
 +
* Phillip Torrone, Make and Adafruit Industries
 +
* Thinh Nguyen, Creative Commons
 +
* Tom Igoe, ITP and Arduino
 +
* Zach Smith, MakerBot
  
{{:OSHW/endorsements}}
+
These people haven't necessarily endorsed the definition, but all had a hand in helping to draft it.

Please note that all contributions to Definition of Free Cultural Works are considered to be released under the Attribution 2.5 (see Definition of Free Cultural Works:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)

Templates used on this page: