Open Source Hardware Gets Defined
Industry leaders in open source hardware draft the parameters.
Members of the open source hardware community publicly issued a list of standards that define a specific piece of hardware as open source. Among the signatures on the document were MIT Media Lab and Arduino lead software developer David Mellis, Adafruit founder Limor Fried, Creative Commons VP of Science John Wilbanks, and Wired editor and DIY Drones founder Chris Anderson.
There are eleven tenets to the open source hardware definition. From the definition:
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 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.
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.
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.
Anyone versed with creative commons will find this list familiar. The full definition and full list of endorsers can be found at http://freedomdefined.org/OSHW.
OpenSource HardwareOpen Source Hardware ... hmmm....
Is that like Open Source Software ...
Can we go somewhere and get it free?, I don't expect to download it.
Can we get the parts for free and build it ourselves; could we even pay for the parts and build it ourselves with either no requirement for a wave-solderer or it being bigger than a breadbox - doubt it.
Will someone else build it and give it away (like I do with my Programs and numerous Patches) like people do with bottled water at the beach or will it arrive in all our mailboxes as a free sample.
It simply to be less expensive since there are no development costs, that is not such a great deal since I can get a used Computer or a Cell Phone for free already AND there is 'some' support from the Manufacturer, User Groups, and of course MY "Programs and numerous Patches" that no one pays for ...
If people want Software for free then they will surely want Hardware for free too - but without profit then why, somehow, someone will pay - will it be "Ad-Hardware" much like some Software is "Ad-Ware", who likes that.
Does not get it,
I likeIt's about time they came out with this. I used to read about opensource hardware a very long time ago and back then it was just a dream. As a software developer I can now actually start using hardware and build them the same way (in matter of licenses) as the software.
Keep up the good work and keep informing the masses about these new developments.
Popular open source encryption tool is vulnerable to attack
New “Yakkety Yak” edition emphasizes cloud and servers
Google finally enters the phone hardware business.
Innovative system adds a hard drive and Ubuntu Core to the RPi for an IoT hub.
Linux is two weeks younger than we thought!
The Apache Software Foundation considers retiring OpenOffice
Adobe won’t kill the plugin in 2017
Linux Foundation's big event celebrates the 25th anniversary of Linux
Linux has evolved from “won’t be a professional” project to one of the most professional software projects in the history of computers.