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!

Difference between revisions of "OSHW"

From Definition of Free Cultural Works
Jump to navigation Jump to search
m (logo to the top)
 
(773 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
== Open Source Hardware (OSHW) Draft Definition version 0.3 ==
+
[[File:Oshw-logo.png|thumb|[[#Logo repository|The Open Source Hardware Logo]]]]
 +
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.
  
''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].''
+
To endorse the Open Source Hardware Definition 1.0, please add your name (and affiliation) [[#Endorsements|below]].
''Videos and Documentation of the Opening Hardware workshop which kicked off the below license are available [http://www.eyebeam.org/projects/Opening-hardware here]''
+
 
 +
[[OSHW older drafts|Older drafts of the definition are also available]].
 +
 
 +
Compiled community feedback from previous versions of the Definition can be found [http://www.openhardwaresummit.org/compiled-feedback/ here]
 +
 
 +
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.
 +
 
 +
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]''
 +
 
 +
== Open Source Hardware (OSHW) Statement of Principles 1.0 ==
 +
 
 +
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 1.0 ==
 +
 
 +
''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].''
 +
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]''
  
 
'''Introduction'''
 
'''Introduction'''
Line 8: Line 25:
 
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.
 
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.
+
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.
  
 
The distribution terms of Open Source Hardware must comply with the following criteria:
 
The distribution terms of Open Source Hardware must comply with the following criteria:
Line 14: Line 31:
 
'''1. Documentation'''
 
'''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.
+
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.  
  
'''2. Necessary Software'''
+
'''3. 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.
+
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:
  
'''3. Derived Works'''
+
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.
  
The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original hardware.  The license must allow for the manufacture, sale, distribution, and use of products created from the design files or derivatives of the design files.
+
b) The necessary software is released under an [http://www.opensource.org/ 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 thereof.
 
   
 
   
'''4. Free redistribution'''
+
'''5. 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.
+
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.
  
'''5. Attribution'''
+
'''6. 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.
+
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.
  
'''6. No Discrimination Against Persons or Groups'''
+
'''7. 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.
  
'''7. No Discrimination Against Fields of Endeavor'''
+
'''8. 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.
+
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.
  
'''8. Distribution of License'''
+
'''9. 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.
+
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.
  
'''9. License Must Not Be Specific to a Product'''
+
'''10. 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.
+
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.
  
'''10. License Must Not Restrict Other Hardware or Software'''
+
'''11. 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.
+
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.
  
'''11. License Must Be Technology-Neutral'''
+
'''12. License Must Be Technology-Neutral'''
  
No provision of the license may be predicated on any individual technology or style of interface.  
+
No provision of the license may be predicated on any individual technology, specific part or component, material, or style of interface or use thereof.  
  
  
Line 62: Line 87:
 
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.
 
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.
  
== Endorsements ==
+
== Licenses and 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:
 +
 
 +
:''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.''
 +
 
 +
== Translations ==
 +
 
 +
The below translations have been offered by members of the community and should be checked for accuracy and possible language problems.
 +
 
 +
{{:OSHW/translations}}
 +
 
 +
== Logo repository ==
  
OSHW Draft Definition 0.3 is endorsed by the following persons and/or organizations.  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.
+
The open source hardware logo lives at [http://www.oshwa.org/open-source-hardware-logo/ oshwa.org].
  
* David A. Mellis, MIT Media Lab and Arduino
+
{{:OSHW/endorsements}}
* Limor Fried, Adafruit Industries
 
* Phillip Torrone, Make and Adafruit Industries
 
* Leah Buechley, MIT Media Lab
 
* Chris Anderson, Wired and DIY Drones
 
* Nathan Seidle, SparkFun Electronics
 
* Alicia Gibb, Bug Labs
 
* Massimo Banzi, Arduino
 
* Tom Igoe, Arduino, ITP/NYU
 
* Zach Smith, MakerBot Industries
 
* Bre Pettis, makerBot Industries
 
* Andrew "bunnie" Huang, bunniestudios
 
* Becky Stern, MAKE
 
* Windell Oskay, Evil Mad Scientist Laboratories
 
* John Wilbanks, Creative Commons
 
* 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
 
* Dave Hrynkiw, Solarbotics Ltd. / HVW Technologies
 
* Stephen Eaton, Strobotics, Australia
 
* Brent Picasso, Autosport Labs
 
* Will Pickering, FunGizmos
 
* Ronen Kadushin, Open Design
 
* Aaron Nielsen, .:oomlout:.
 
* Jay Woods, Woods R&E
 

Latest revision as of 09:56, 14 June 2020

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.

To endorse the Open Source Hardware Definition 1.0, please add your name (and affiliation) below.

Older drafts of the definition are also available.

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

If you would like to propose changes to the statement of principles or definition, please do so on the work-in-progress draft. And, please edit while signed in, not anonymously.

Please join the conversation about the definition here

Open Source Hardware (OSHW) Statement of Principles 1.0[edit]

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 1.0[edit]

OSHW Draft Definition 1.0 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.

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.

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

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[edit]

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. Patents 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:

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.

Translations[edit]

The below translations have been offered by members of the community and should be checked for accuracy and possible language problems.

(Edit)

Logo repository[edit]

The open source hardware logo lives at oshwa.org.

Endorsements[edit]

OSHW Draft Definition 1.0 has been endorsed by the following persons and/or organization as of 2020/06/14.

Please feel free to add (your own) name 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