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
Line 1: Line 1:
{{divbox|1=gray|2=Please Note:|3=This page contains the preliminary versions of the open source hardware definition created in 2010 by a large number of people on the Open Hardware Eyebeam and OSHW mailing lists. New versions of the definition are no longer made in this wiki and the text of this definition is not updated. Updated versions of the definition have been produced by OSHWA and are available at [http://www.oshwa.org/definition http://www.oshwa.org/definition].}}
 
 
----
 
 
 
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.
 
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.
  
Line 12: Line 8:
  
 
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.
 
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 (OSHW) Statement of Principles 1.0 ==
Line 102: Line 101:
 
== Logo repository ==
 
== Logo repository ==
  
The open source hardware logo lives at [http://www.oshwa.org/open-source-hardware-logo/ oshwa.org].
+
The open source hardware logo lives at [http://oshwlogo.com oshwlogo.com].
  
 
http://i1166.photobucket.com/albums/q601/H3rlihy/OSH_Steellowres.jpg
 
http://i1166.photobucket.com/albums/q601/H3rlihy/OSH_Steellowres.jpg
Line 112: Line 111:
 
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 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 [http://www.oshwa.org/forums/forum/open-source-hardware-definition-discussion/ here]''
+
''Please join the conversation about the definition [http://openhardwaresummit.org/forum here]''
  
 
* Aaron Clarke, [http://AaronClarke.com] [http://blog.EmbeddedCoding.com EmbeddedCoding.com]
 
* Aaron Clarke, [http://AaronClarke.com] [http://blog.EmbeddedCoding.com EmbeddedCoding.com]
Line 124: Line 123:
 
* Adviye Ayça Ünlüer [http://www.yildiz.edu.tr Yildiz Technical University]
 
* Adviye Ayça Ünlüer [http://www.yildiz.edu.tr Yildiz Technical University]
 
* Ahmet Alpat, [http://arduinoturkiye.com Arduino Türkiye] [http://ahmetalpat.com Elektrik, Elektronik, Enerji]
 
* Ahmet Alpat, [http://arduinoturkiye.com Arduino Türkiye] [http://ahmetalpat.com Elektrik, Elektronik, Enerji]
* AJ Quick [http://www.aquickcnc.com A Quick CNC]
 
 
* Akiba, [http://www.freaklabs.org/ FreakLabs]
 
* Akiba, [http://www.freaklabs.org/ FreakLabs]
* Akshai M [http://www.microhope.org/ MicroHOPE Foundation]
 
* Alan Pack [http://photoboothking.com.au Photo Booth King]
 
 
* Albert Monés [http://www.replicat.es replicat.es]
 
* Albert Monés [http://www.replicat.es replicat.es]
 
* Alberto Fabiano [https://garoa.net.br/wiki/Noite_do_Arduino Garoa Hacker Clube]
 
* Alberto Fabiano [https://garoa.net.br/wiki/Noite_do_Arduino Garoa Hacker Clube]
Line 140: Line 136:
 
* André Menks [http://multilogica-shop.com/ Multilógica-shop]
 
* André Menks [http://multilogica-shop.com/ Multilógica-shop]
 
* Andreas Olofsson [http://www.parallella.org Parallella]
 
* Andreas Olofsson [http://www.parallella.org Parallella]
* Andrés Delgado [http://aperturaradical.org Apertura Radical]
 
 
* Andrew Back [http://oshug.org Open Source Hardware User Group]
 
* Andrew Back [http://oshug.org Open Source Hardware User Group]
 
* Andrew Katz [http://www.moorcrofts.com Moorcrofts LLP]
 
* Andrew Katz [http://www.moorcrofts.com Moorcrofts LLP]
Line 153: Line 148:
 
* Anool Mahidharia [http://www.wyolum.com/ WyoLum]
 
* Anool Mahidharia [http://www.wyolum.com/ WyoLum]
 
* Anthony Clay, [http://www.zarthcode.com ZarthCode LLC]
 
* Anthony Clay, [http://www.zarthcode.com ZarthCode LLC]
* Antoine C., [http://fr-voosilla.ouvaton.org/ Projet Voosilla]
 
* Arno Eikhof, [http://uvc.de/ UVC Ingenieure]
 
 
* Arthur Wolf, [http://smoothieware.org Smoothie]
 
* Arthur Wolf, [http://smoothieware.org Smoothie]
 
* Asim Baig, [http://www.tinkeract.com/ Tinkeract]
 
* Asim Baig, [http://www.tinkeract.com/ Tinkeract]
 
* Ayah Bdeir, [http://www.littleBits.cc littleBits.cc]/[http://www.eyebeam.org Eyebeam]/[http://www.creativecommons.org Creative Commons]
 
* Ayah Bdeir, [http://www.littleBits.cc littleBits.cc]/[http://www.eyebeam.org Eyebeam]/[http://www.creativecommons.org Creative Commons]
* Balestrino Salvatore [http://oshw.it OSHW.IT]
 
 
* Bastian Bittorf [http://bittorf-wireless.de/ bittorf wireless ))]
 
* Bastian Bittorf [http://bittorf-wireless.de/ bittorf wireless ))]
 
* Ben Leduc-Mills [http://l3d.cs.colorado.edu/~ctg/Craft_Tech.html Craft Technology Lab]
 
* Ben Leduc-Mills [http://l3d.cs.colorado.edu/~ctg/Craft_Tech.html Craft Technology Lab]
Line 178: Line 170:
 
* Brian Rayburn
 
* Brian Rayburn
 
* Brian Harling, [http://modtronicsaustralia.com/ Modtronics Australia]
 
* Brian Harling, [http://modtronicsaustralia.com/ Modtronics Australia]
* Briana Mansion,[http://www.tenderoo.com Tenderoo]
 
 
* Bryan Bishop, [http://gnusha.org/skdb/ SKDB] [http://humanityplus.org/ Humanity+]
 
* Bryan Bishop, [http://gnusha.org/skdb/ SKDB] [http://humanityplus.org/ Humanity+]
 
* bunnie [http://bunniestudios.com/ bunniestudios]
 
* bunnie [http://bunniestudios.com/ bunniestudios]
* Cade Klock
 
 
* Carmen Gonzalez, [http://opensolarcircuits.cc] DreamAddictive
 
* Carmen Gonzalez, [http://opensolarcircuits.cc] DreamAddictive
 
* Carmen Trudell [http://www.fluxxlab.com Fluxxlab]
 
* Carmen Trudell [http://www.fluxxlab.com Fluxxlab]
* Carol Willing
 
 
* Carson Reynolds [http://www.k2.t.u-tokyo.ac.jp/members/carson/carson-e.html University of Tokyo]
 
* Carson Reynolds [http://www.k2.t.u-tokyo.ac.jp/members/carson/carson-e.html University of Tokyo]
 
* Catarina Mota, [http://openmaterials.org openMaterials]
 
* Catarina Mota, [http://openmaterials.org openMaterials]
Line 194: Line 183:
 
* Charles Yarnold
 
* Charles Yarnold
 
* Chris Anderson, [http://www.diydrones.com/ 3D Robotics/DIY Drones]
 
* Chris Anderson, [http://www.diydrones.com/ 3D Robotics/DIY Drones]
* Chris Harris [http://agency1.com.au Agency1]
 
* Chris Mark [http://www.fellers.com.au Fellers Tree Services]
 
 
* Chris Jefferies, Tinaja Labs
 
* Chris Jefferies, Tinaja Labs
 
* Chris Novello, [http://www.illucia.com/ illucia instruments]
 
* Chris Novello, [http://www.illucia.com/ illucia instruments]
Line 225: Line 212:
 
* Demetris Rouslan Zavorotnitsienko [http://www.gizmoforyou.com/ GizmoForYou]
 
* Demetris Rouslan Zavorotnitsienko [http://www.gizmoforyou.com/ GizmoForYou]
 
* Diego Spinola [http://www.hackeneering.com/ Hackeneering]
 
* Diego Spinola [http://www.hackeneering.com/ Hackeneering]
* Dilshan R Jayakody [http://jayakody2000lk.blogspot.com Dilshan R Jayakody’s Web Log]
+
* Dilshan R Jayakody [http://jayakody.info jayakody.info]
 
* Dimitri Albino [http://smartmaker.org smARtMAKER]
 
* Dimitri Albino [http://smartmaker.org smARtMAKER]
 
* D'sun Labs [http://dsunlabs.com/]
 
* D'sun Labs [http://dsunlabs.com/]
Line 263: Line 250:
 
* Guo haoyun [http://bjmakerspace.com/]
 
* Guo haoyun [http://bjmakerspace.com/]
 
* Gustav Karlsson [http://www.karlssonrobotics.com/ Karlsson Robotics]
 
* Gustav Karlsson [http://www.karlssonrobotics.com/ Karlsson Robotics]
* Hal Gottfried [http://www.kcohg.org KC Open Hardware Society]
 
 
* Hannah Perner-Wilson [http://www.plusea.at Plusea] [http://www.howtogetwhatyouwant.at How To Get What You Want]
 
* Hannah Perner-Wilson [http://www.plusea.at Plusea] [http://www.howtogetwhatyouwant.at How To Get What You Want]
 
* Hans Scharler [http://iobridge.com ioBridge] [http://thingspeak.com ThingSpeak]
 
* Hans Scharler [http://iobridge.com ioBridge] [http://thingspeak.com ThingSpeak]
Line 289: Line 275:
 
* Jean-Marc Giacalone, [http://www.emakershop.com eMAKERshop]
 
* Jean-Marc Giacalone, [http://www.emakershop.com eMAKERshop]
 
* Jeff Karney [http://jkdevices.com JK Devices]
 
* Jeff Karney [http://jkdevices.com JK Devices]
* Jenny Kellett [http://loudclear.com.au Loud&Clear]
 
 
* Jeff Keyzer [http://mightyohm.com MightyOhm Engineering]
 
* Jeff Keyzer [http://mightyohm.com MightyOhm Engineering]
 
* Jeff Moe, [http://www.alephobjects.com/ Aleph Objects, Inc.]
 
* Jeff Moe, [http://www.alephobjects.com/ Aleph Objects, Inc.]
Line 313: Line 298:
 
* Jorel Lalicki, [http://lib3.com/ LIB3 Inc.- Open Source Hardware for Experimenters]
 
* Jorel Lalicki, [http://lib3.com/ LIB3 Inc.- Open Source Hardware for Experimenters]
 
* Jorge Alberto Silva [http://www.cdiritesco.mx/ CDIR ITESCO]
 
* Jorge Alberto Silva [http://www.cdiritesco.mx/ CDIR ITESCO]
* Jose A. Barreiros, [http://southmade.org South Made, Ecuadorian Open Hardware Community]
 
 
* Jose M. de la Fuente [http://n00b0t.tikitake.com/ n00b0t][http://mm8.tikitake.com/ mm8]
 
* Jose M. de la Fuente [http://n00b0t.tikitake.com/ n00b0t][http://mm8.tikitake.com/ mm8]
 
* Josef Pruša [http://josefprusa.cz] RepRap developer
 
* Josef Pruša [http://josefprusa.cz] RepRap developer
Line 340: Line 324:
 
* Lubos Medovarsky, [http://accelera-networks.com Accelera Networks]
 
* Lubos Medovarsky, [http://accelera-networks.com Accelera Networks]
 
* Luigi Carnevale, [http://www.droids.it/ Droids]
 
* Luigi Carnevale, [http://www.droids.it/ Droids]
* Maik Kroka, [https://www.dischereit.de/ Dischereit SMT Assembly]
 
 
* Marcin Jakubowski, [http://opensourceecology.org/ Open Source Ecology]
 
* Marcin Jakubowski, [http://opensourceecology.org/ Open Source Ecology]
 
* Marcus A. Link [http://www.manupool.de Manupool - A Product Development Community]
 
* Marcus A. Link [http://www.manupool.de Manupool - A Product Development Community]
 
* Mario Behling, [http://mbm.vn/ MBM]
 
* Mario Behling, [http://mbm.vn/ MBM]
* Mario Raul Perez, [http://macroplc.com/ MacroPLC]
 
 
* Mario Vernari, [http://highfieldtales.wordpress.com/ Highfieldtales]
 
* Mario Vernari, [http://highfieldtales.wordpress.com/ Highfieldtales]
 
* Mark Carew, [http://openbuilds.org OpenBuilds]
 
* Mark Carew, [http://openbuilds.org OpenBuilds]
* Mark Khusid, EE, [http://markkhusid.ddns.net MK Dynamics]
 
 
* Mark McComb, [http://www.hacktronics.com/ hacktronics]
 
* Mark McComb, [http://www.hacktronics.com/ hacktronics]
 
* Marty Schrader, [http://www.parsecsystemsinc.com/ Parsec Technologies, Inc.]
 
* Marty Schrader, [http://www.parsecsystemsinc.com/ Parsec Technologies, Inc.]
 
* Massimo Banzi [http://www.arduino.cc Arduino]
 
* Massimo Banzi [http://www.arduino.cc Arduino]
 
* Mathilde Berchon [http://www.makingsociety.com MakingSociety]
 
* Mathilde Berchon [http://www.makingsociety.com MakingSociety]
* Matija Šuklje [http://fsfe.org FSFE] [http://lugos.si LUGOS] [http://www.kiberpipa.org Cyberpipe hackerspace]
 
 
* Mats Engstrom [http://www.smallroomlabs.com SmallRoomLabs]
 
* Mats Engstrom [http://www.smallroomlabs.com SmallRoomLabs]
 
* Mats Undén
 
* Mats Undén
Line 359: Line 339:
 
* Matthew Slater [http://communityforge.net Community Forge]
 
* Matthew Slater [http://communityforge.net Community Forge]
 
* Matthieu Quadrini [http://openscb.org OpenSCB]
 
* Matthieu Quadrini [http://openscb.org OpenSCB]
* Michael Eber [http://www.makertronic.com Makertronic]
 
 
* Michael James [http://opensourcehardwarejunkies.com OSHJunkies]
 
* Michael James [http://opensourcehardwarejunkies.com OSHJunkies]
 
* Michael Krumpus [http://nootropicdesign.com/ nootropic design]
 
* Michael Krumpus [http://nootropicdesign.com/ nootropic design]
Line 368: Line 347:
 
* Mitch Altman [http://cornfieldelectronics.com/ Cornfield Electronics]
 
* Mitch Altman [http://cornfieldelectronics.com/ Cornfield Electronics]
 
* Mitch Patterson(mitpatterson) [http://mitchstechblog.wordpress.com/ Mitch's Tech Blog]
 
* Mitch Patterson(mitpatterson) [http://mitchstechblog.wordpress.com/ Mitch's Tech Blog]
* Mohamed [http://www.asensar.com/ aSensar] [http://www.RepRap-India.com/ RepRap-India]
 
 
* Morgaine Dinova [[User:Morgaine_Dinova|[1]]], lecturer and consultant
 
* Morgaine Dinova [[User:Morgaine_Dinova|[1]]], lecturer and consultant
 
* Moritz von Buttlar [http://www.opensource-solar.org/ Opensource-Solar]
 
* Moritz von Buttlar [http://www.opensource-solar.org/ Opensource-Solar]
Line 382: Line 360:
 
* Nuri Erginer [http://www.gnexlab.com/ gnexlab]
 
* Nuri Erginer [http://www.gnexlab.com/ gnexlab]
 
* Oldrich Horacek [http://hwkitchen.com/ HW Kitchen]
 
* Oldrich Horacek [http://hwkitchen.com/ HW Kitchen]
* Ondrej Zizka
 
 
* Oguz Alp Tan [http://www.oguzalptan.com/ SEO ideas]
 
* Oguz Alp Tan [http://www.oguzalptan.com/ SEO ideas]
 
* Paolo Patierno, [http://dotnetcampania.org/blogs/paolopat/default.aspx DevExperience]
 
* Paolo Patierno, [http://dotnetcampania.org/blogs/paolopat/default.aspx DevExperience]
Line 398: Line 375:
 
* Pierrick Boissard [http://igrebot.fr/ I-Grebot robotics association]
 
* Pierrick Boissard [http://igrebot.fr/ I-Grebot robotics association]
 
* Pip Jones [http://www.deepend.com.au Deepend]
 
* Pip Jones [http://www.deepend.com.au Deepend]
* Pradeep Sharma, [https://www.robomart.com/arduino-uno-online-india Arduino UNO India]
 
 
* Prashant Khandelwal [http://midnightprogrammer.net midnightprogrammer.net]
 
* Prashant Khandelwal [http://midnightprogrammer.net midnightprogrammer.net]
 
* R. Scott Plunkett, [http://www.openqi.com/ The OpenQi Project]  
 
* R. Scott Plunkett, [http://www.openqi.com/ The OpenQi Project]  
Line 411: Line 387:
 
* Red Byer [http://www.redstoyland.com Red's Toyland]
 
* Red Byer [http://www.redstoyland.com Red's Toyland]
 
* Richard Anderson [http://fubarlabs.com Fair Use Building and Research Labs]
 
* Richard Anderson [http://fubarlabs.com Fair Use Building and Research Labs]
* Richard Arnett [http://chromatograDIY.wordpress.com ChromatograDIY]
 
 
* Robert Fitzsimons [http://partfusion.com/ Part Fusion Electronics]
 
* Robert Fitzsimons [http://partfusion.com/ Part Fusion Electronics]
 
* Robit Technology [http://www.robitshop.com/ Parts of Electronics and Robotics]
 
* Robit Technology [http://www.robitshop.com/ Parts of Electronics and Robotics]
* Rodolfo Cossovich [http://multiplo.org/ Multiplo]
 
 
* Ron K. Jeffries, Jeffries Research
 
* Ron K. Jeffries, Jeffries Research
 
* Ronen Kadushin [http://www.ronen-kadushin.com/Open_Design.asp Open Design]
 
* Ronen Kadushin [http://www.ronen-kadushin.com/Open_Design.asp Open Design]
Line 430: Line 404:
 
* Stacy L. Devino, [http://doesitpew.blogspot.com/ Does it Pew?][http://www.stacydevino.com/ aka childofthehorn]
 
* Stacy L. Devino, [http://doesitpew.blogspot.com/ Does it Pew?][http://www.stacydevino.com/ aka childofthehorn]
 
* Sterling Pickens, [http://www.linuxsociety.org/ linuxsociety]
 
* Sterling Pickens, [http://www.linuxsociety.org/ linuxsociety]
* Steve Demian, [http://www.em.com.au/ em creative/digital]
 
 
* Steve Dickie, [http://www.arduinoeducation.com/ ArduinoEducation.com]
 
* Steve Dickie, [http://www.arduinoeducation.com/ ArduinoEducation.com]
 
* Steve Gifford, [http://www.chipstobits.com Chips To Bits]
 
* Steve Gifford, [http://www.chipstobits.com Chips To Bits]
 
* Steve Hoefer [http://grathio.com/ Grathio Labs]
 
* Steve Hoefer [http://grathio.com/ Grathio Labs]
 
* Stewart Dickson [http://makerspaceu.org  Makerspace-Urbana]
 
* Stewart Dickson [http://makerspaceu.org  Makerspace-Urbana]
* Suniel Kumar G, [http://www.POSHLabs.org/ POSHLabs-People's Open Source Hardware Labs]
 
 
* Tassos Natsakis [http://kuleuven.be KU Leuven]
 
* Tassos Natsakis [http://kuleuven.be KU Leuven]
* Taylor Alexander [http://flutterwireless.com Flutter Wireless]
 
 
* Terry King, [http://www.arduino-direct.com/sunshop/ YourDuino.com]  
 
* Terry King, [http://www.arduino-direct.com/sunshop/ YourDuino.com]  
 
* Thalis Antunes [http://www.facit.edu.br FACIT]
 
* Thalis Antunes [http://www.facit.edu.br FACIT]
 
* Theodore Ullrich, [http://tomorrow-lab.com Tomorrow Lab™]
 
* Theodore Ullrich, [http://tomorrow-lab.com Tomorrow Lab™]
 
* Thomas Gokey, [http://thomasgokey.com/ artist]
 
* Thomas Gokey, [http://thomasgokey.com/ artist]
* Thomas McGahee--[[Special:Contributions/206.41.39.34|206.41.39.34]] 13:20, 18 May 2014 (EDT)
 
 
* Tim Lossen, [http://evercu.be Evercube]
 
* Tim Lossen, [http://evercu.be Evercube]
 
* Tom Igoe, [http://www.arduino.cc Arduino] [http://itp.nyu.edu ITP, NYU]
 
* Tom Igoe, [http://www.arduino.cc Arduino] [http://itp.nyu.edu ITP, NYU]
Line 452: Line 422:
 
* Tushar Makwana, [http://www.explorelabs.com/ Explore Labs]
 
* Tushar Makwana, [http://www.explorelabs.com/ Explore Labs]
 
* Usman Haque, [http://www.pachube.com/ Pachube]
 
* Usman Haque, [http://www.pachube.com/ Pachube]
* Victor Christiansenn, [https://www.secpoint.com SecPoint]
 
* Victor Perin, [http://www.nerdhitech.com.br Nerd Hi-Tech]
 
 
* Viento [http://flydendeby.dk/ Floating City Copenhagen]
 
* Viento [http://flydendeby.dk/ Floating City Copenhagen]
 
* Vlad Trifa, [http://www.webofthings.com Web of Things] [http://vladtrifa.com ETH Zurich]
 
* Vlad Trifa, [http://www.webofthings.com Web of Things] [http://vladtrifa.com ETH Zurich]
Line 459: Line 427:
 
* Will Pickering, [http://www.FunGizmos.com FunGizmos]
 
* Will Pickering, [http://www.FunGizmos.com FunGizmos]
 
* William Morris, [http://www.iheartrobotics.com I Heart Robotics]/[http://www.iheartengineering.com I Heart Engineering]
 
* William Morris, [http://www.iheartrobotics.com I Heart Robotics]/[http://www.iheartengineering.com I Heart Engineering]
* William Zain, [http://www.mobooth.com.au/ MoBooth]
 
 
* Wim Vandeputte, [http://kd85.com kd85]
 
* Wim Vandeputte, [http://kd85.com kd85]
 
* Windell Oskay, [http://evilmadscience.com/ Evil Mad Science]
 
* Windell Oskay, [http://evilmadscience.com/ Evil Mad Science]
 
* Yannick Avelino, [http://www.electrolab.fr/ Electrolab]
 
* Yannick Avelino, [http://www.electrolab.fr/ Electrolab]
 
* Yoonseo Kang, [http://opentechforever.com/ Open Tech Forever]
 
* Yoonseo Kang, [http://opentechforever.com/ Open Tech Forever]
* Xavier Leonard, [http://www.XdotL.com/ X.L]
 
 
* Zhang Dong,[http://www.homemode.me HOMEMODE]
 
* Zhang Dong,[http://www.homemode.me HOMEMODE]

Revision as of 02:54, 26 May 2016

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

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

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

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

(Edit)

Logo repository

The open source hardware logo lives at oshwlogo.com.

OSH_Steellowres.jpg

Endorsements

OSHW Draft Definition 1.0 has been endorsed by the following persons and/or organization as of 2016/05/26.

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