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 draft
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 publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
This page hosts the | This page hosts the current proposed Open Source Hardware (OSHW) Draft Statement of Principles and Definition. 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. | ||
The widely endorsed definition draft 0.3 is on [http://freedomdefined.org/OSHW this page]; [http://freedomdefined.org/OSHW_older_drafts older drafts are also available]. | |||
[http://freedomdefined.org/OSHW | |||
If you would like to propose changes to the statement of principles or definition by editing this page, please do so with extreme care and consideration; this draft definition has been crafted with the input of many individuals with diverse backgrounds and points of view. (And, please edit while signed in, not anonymously.) | |||
If you would like to propose changes to the statement of principles or definition, please edit while signed in, not anonymously. | |||
== Open Source Hardware (OSHW) Statement of Principles (Draft) == | |||
Open-source hardware is something you can make for yourself, modify the design of, make modified versions of, and distribute for others to use. To do this, you need access to the hardware's source (the digital files from which it's made) in the preferred format for modifying it: for example, CAD files for circuit boards or mechanical parts and source code for supporting software. You also need access to the infrastructure and content that the device relies on. You need to be able to get the components used in the hardware and to sell the hardware once you've made it. These things together provide individuals with the freedom to control their products and adapt them to their needs. | |||
== Open Source Hardware (OSHW) Definition | == Open Source Hardware (OSHW) Definition (Draft Version 0.4) == | ||
''OSHW Draft Definition | ''OSHW Draft Definition 0.4 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.3]. 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]'' | ''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]'' | ||
Line 31: | Line 26: | ||
'''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 format for making changes, for example the native file format of a CAD program. | 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''' | '''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 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, provided that the license does not require the use of these non-open components. | ||
'''3. Necessary Software''' | '''3. Necessary Software''' | ||
If the | If the hardware released under the license 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. | 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 be 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. | b) The necessary software is released under an OSI-approved open source license. | ||
Line 47: | Line 42: | ||
'''4. Derived Works''' | '''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 | 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. | ||
'''5. Free redistribution''' | '''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. | 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. | ||
'''6. Attribution''' | '''6. Attribution''' | ||
The license may require derived | 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. | ||
'''7. No Discrimination Against Persons or Groups''' | '''7. No Discrimination Against Persons or Groups''' | ||
Line 63: | Line 58: | ||
'''8. No Discrimination Against Fields of Endeavor''' | '''8. No Discrimination Against Fields of Endeavor''' | ||
The license must not restrict anyone from making use of the | The license must not restrict anyone from making use of the 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''' | '''9. Distribution of License''' | ||
The rights | 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. | ||
'''10. License Must Not Be Specific to a Product''' | '''10. License Must Not Be Specific to a Product''' | ||
The rights | 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. | ||
'''11. 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 | 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. | ||
'''12. License Must Be Technology-Neutral''' | '''12. License Must Be Technology-Neutral''' | ||
Line 87: | Line 82: | ||
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 == | ||
This OSHW Draft Definition (0.4) is under active discussion and editing at the present time. Please do not endorse this definition, as it may still change. If you feel that the present version is "golden," and would like to endorse it as-is, please (1) move it to the [http://freedomdefined.org/OSHW_older_drafts old draft page] and endorse it there and (2) increment the version number as shown on this page (from 0.4 to 0.5, for example) so that others may continue making changes under the new version number. | |||
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]'' | ''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]'' |