OSHW older drafts

Old drafts of OSHW definition

IMPORTANT: This page is a repository for older, deprecated drafts of the Open-Source Hardware definition.

For the current version, please instead go here. Or see the work-in-progress draft.

Compiled community feedback from previous versions of the Definition can be found here

Please do not modify the definitions on this page, as they have been endorsed by individuals in their present form.

Open Source Hardware (OSHW) Statement of Principles (Draft 0.5)

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.

Open Source Hardware (OSHW) Definition (Draft Version)

OSHW Draft Definition 0.4 is based on the Open Source Definition for Open Source Software and draft OSHW definition 0.5. The definition is derived from the 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 here. Please join the conversation about the definition here

Introduction

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.

It is important to note that 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 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 distribution terms of Open Source Hardware must comply with the following criteria:

1. Documentation

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).

2. Scope

The documentation for the hardware must clearly specify what portion of the design, if not all, is being released under the license.

3. Necessary Software

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:

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.

b) The necessary software is released under an OSI-approved open source license.

4. 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 therof.

5. Free redistribution

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.

6. 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.

7. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

8. 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

No provision of the license may be predicated on any individual technology, specific part or component, material, or style of interface or use thereof.

Afterword

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.

Licenses and Hardware

In promoting Open Hardware, it is important not to unintentionally deceive designers regarding 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. Patents do. The result is that an Open Hardware license can in general be used to restrict the plans but probably 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:

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.

Open Source Hardware (OSHW) Statement of Principles (Draft)

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.

Open Source Hardware (OSHW) Definition (Draft Version 0.4)

OSHW Draft Definition 0.4 is based on the Open Source Definition for Open Source Software and draft OSHW definition 0.3. The definition is derived from the 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 here. Please join the conversation about the definition here

Introduction

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.

It is important to note that 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 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 distribution terms of Open Source Hardware must comply with the following criteria:

1. Documentation

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).

2. Scope

The documentation for the hardware must clearly specify what portion of the design, if not all, is being released under the license. The license may restrict the bill of materials to components which are generic, open-source, or otherwise non-proprietary. Alternatively, the design may incorporate the use of non-open components, for example if a manufacturer releases the design for a development board that incorporates a proprietary integrated circuit. The license may not require that any specific components, goods or services be used.

3. Necessary Software

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:

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.

b) The necessary software is released under an OSI-approved open source license.

4. 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 therof.

5. Free redistribution

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.

6. 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.

7. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

8. 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

No provision of the license may be predicated on any individual technology, specific part or component, material, or style of interface or use thereof.

Afterword

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.

Licenses and Hardware

In promoting Open Hardware, it is important not to unintentionally deceive designers regarding 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. Patents do. The result is that an Open Hardware license can in general be used to restrict the plans but probably 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:

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.

Open Source Hardware (OSHW) Draft Definition version 0.3

OSHW Draft Definition 0.3 is based on the Open Source Definition for Open Source Software and draft OSHW definition 0.2. The definition is derived from the 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 here. Please join the conversation about the definition here

Introduction

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.

It is important to note that 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 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 distribution terms of Open Source Hardware must comply with the following criteria:

1. Documentation

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 analogous to compiled computer code -- such as printer-ready copper artwork from a CAD program -- are not allowed as substitutes.

2. Necessary Software

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 OSI-approved 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.

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 hardware. The license shall allow for the manufacture, sale, distribution, and use of products created from the design files or derivatives of the design files.

4. Free redistribution

The license shall not restrict any party from selling or giving away the project documentation as a component of an aggregate distribution containing designs from several different sources. 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.

5. Attribution

The license may require derived works to provide attribution to the original designer when distributing design files, manufactured products, and/or derivatives thereof. The license may also require derived works to carry a different name or version number from the original design.

6. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

7. No Discrimination Against Fields of Endeavor

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.

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

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.

10. License Must Not Restrict Other Hardware or Software

The license must not place restrictions on other hardware or software that may be distributed or used 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.

11. License Must Be Technology-Neutral

No provision of the license may be predicated on any individual technology or style of interface.

Afterword

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.

You’re a real deep thinker. Thanks for sharnig.

Definition version 0.1

(This version has been endorsed by several individuals; please do not modify.)

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.

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

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

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.

Signatories of version 0.3

OSHW Draft Definition 0.3 has been endorsed by the following persons and/or organization as of September 22, 2010.

Please feel free to add (your own names) to this section. Listing your affiliation is optional for personal endorsements, and endorsements are presumed to be personal unless the organization name is listed separately.

Please join the conversation about the definition here

• David A. Mellis, MIT Media Lab and Arduino
• Leah Buechley, MIT Media Lab
• Nathan Oostendorp, SourceForge.net
• John Wilbanks, Creative Commons
• Limor Fried, Adafruit Industries
• Phillip Torrone, Make / Adafruit Industries
• Chris Anderson, Wired / DIY Drones
• Nathan Seidle, SparkFun Electronics
• Massimo Banzi, Arduino
• Tom Igoe, Arduino / ITP/NYU
• Eric Pan, Seeed Studio
• David Carrier, Parallax Inc.
• Ken Gracey, Parallax Inc.
• Zach Smith, MakerBot Industries
• Bre Pettis, MakerBot Industries
• Justin Huynh Liquidware
• Becky Stern, Make
• Windell Oskay, Evil Mad Scientist Laboratories
• Dave Hrynkiw, Solarbotics Ltd. / HVW Technologies
• Will Pickering, FunGizmos
• Alicia Gibb, Bug Labs
• Frank Piller, RWTH Aachen University
• Jaime Fernández-Caro Belmonte Microingenia Electronics
• Andrew "bunnie" Huang, bunniestudios
• Mitch Altman, Cornfield Electronics
• Jonathan Kuniholm, Open Prosthetics Project/Shared Design Alliance
• Ayah Bdeir, littleBits.cc/Eyebeam/Creative Commons
• David Ford, Blue Labs
• Vitorino Ramos, LaSEEB - Evolutionary Systems and Biomedical Engineering Lab., IST, Technical University of Lisbon, Lisbon, PORTUGAL.
• Charles Gantt, The Makers Workbench
• Raúl Oviedo, Ayuda Electrónica / Spanish License
• Stephen Eaton, Strobotics, Australia
• Brent Picasso, Autosport Labs http://www.autosportlabs.net
• Ronen Kadushin, Open Design [1]
• Aaron Nielsen, .:oomlout:.
• Jay Woods, Woods R&E
• Barton Dring, buildlog.net - Open Source Laser Cutter
• Diego Spinola, Hackeneering
• Shigeru Kobayashi, Gainer and Funnel
• Sean Auriti, Alpha One Labs http://www.alphaonelabs.com
• Shashikiran Ganesh, India
• Sébastien Bourdeauducq, Milkymist
• Paul Youlten, Open Moto X
• Don Wilcher, MaDon Research http://www.family-science.net
• Chris Prince, Regulus Tech
• Daniel Reetz, DIYBookScanner.org
• Harland R. Coles, Energy X Systems Ltd.
• Julián da Silva Gillig, RobotGroup http://robotgroup.com.ar
• Charles Collis, AdCiv.org
• Andy Gelme, Connected Community HackerSpace, Melbourne, Australia and Geekscape Pty. Ltd.
• Jonathan Oxer, Freetronics
• Daniel Garcia, Protostack
• Fletcher McBeth, President, VHDL Inc.
• Joseph S. Terry, Jr., [2]
• Marc Alexander, Freetronics
• Rhys Chinchen, Melbourne VIC Australia
• Florin Cocos, Youritronics
• Catarina Mota, openMaterials
• Bryan Bishop, Open Manufacturing Group
• Lubos Medovarsky, Accelera Networks
• Ben Leduc-Mills, Craft Technology Lab, CU Boulder
• Chris Walker, Secret Labs
• David Gapen, Handmade Circuits
• Tiago Rodrigues, LusoRobótica PORTUGAL
• Michael Stephens, FLAKElabs
• Constantin Craciun, Harkopen.com
• Alessandro Lambardi, 5volt.eu
• Michael Provenzano, CEO Progunn R&D Industries
• Matt Howard, CIO, eTech Ohio
• Michael Eber, CTO, Kineteka Systems / PodGizmo
• Andrew Plumb, ClothBot
• Dominic Muren, The Humblefactory
• Brian Jepson, Jepstone.net
• MakerBlock MakerBlock
• Stefan Hechenberger, Nortd Labs
• Steven Gifford, Chips To Bits
• Roy Mohan Shearer, Openthing
• Paul List, Embedded Journey
• Christian Siefkes, keimform.de
• Kerstin Balka, Open Innovation Projects
• Joe Pardue, Smiley Micros
• Jean Demartini, DEMTECH - FRANCE
• Cathal Garvey, Labs From Fabs
• John Lejeune, Louis Montagne, Wim Vandeputte, hackable-devices.org
• Brandon Stafford, Rascal Micro
• Renato G. S. Barcellos, Information Technology of Federal Fluminense University, BRAZIL
• James A. Barkley ("Jim")
• C. A. Church OpenMoCo.org
• John A. Boxall tronixstuff.com
• Global Professional IC Market ChinaICMart
• Thadeu Lima de Souza Cascardo Holoscópio Tecnologia Ltda., Brazil
• Samuel R. C. Vale Holoscópio Tecnologia Ltda., Brazil
• Jeff Osier-Mixon Jefro.net
• Garrett Mace, CTO macetech
• Global IC Trading Platform SeekIC
• Steve Gifford Chips To Bits
• Alvaro G. S. Barcellos, senior geophysicist, Brasil
• Dustyn Roberts, dustynrobots / NYU ITP
• Thushar V Nadh, rhydoLABZ
• Rich Scherlitz, Electric Chili / Rich Scherlitz
• Chris Gammell, Analog Life, LLC / The Amp Hour
• Akiba, FreakLabs
• Cefn Hoile, Enigmaker
• David Cuartielles, Arduino
• Peter Kirn, Create Digital Music / MeeBlip
• George Hadley NBitWonder
• Kirsty Boyle openMaterials
• David Siren Eisner, InMojo

Please join the conversation about the definition here

Signatories of version 0.1

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
• Leah Buechley, MIT Media Lab

Initial Workshop Participants

This definition originated with discussion between attendees of the Opening Hardware workshop at Eyebeam (New York City), March 17, 2010, in particular (listed alphabetically by first name):

• Alicia Gibb, Bug Labs
• Ayah Bdeir, Eyebeam
• Becky Stern, MAKE
• 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

These people haven't necessarily endorsed the definition, but all had a hand in helping to draft it.