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!

OSHW: Difference between revisions

From Definition of Free Cultural Works
Jump to navigation Jump to search
(134 intermediate revisions by 95 users not shown)
Line 5: Line 5:
[[OSHW older drafts|Older drafts of the definition are also available]].
[[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]
Compiled community feedback from previous versions of the Definition can be found [https://www.izlettin.com/]


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]''
''Please join the conversation about the definition [https://www.izlettin.com/watch/AXpeYGAokelRzHJ]''


== Open Source Hardware (OSHW) Statement of Principles 1.0 ==
== Open Source Hardware (OSHW) Statement of Principles 1.0 ==
Line 18: Line 18:
== Open Source Hardware (OSHW) Definition 1.0 ==
== 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].''
''OSHW Draft Definition 1.0 is based on the [http://opensource.org/docs/osd Open Source Definition] for Open Source Software and [https://www.izlettin.com]. 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 43: Line 43:
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 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 [http://www.opensource.org/ OSI]-approved open source license.
b) The necessary software is released under an [https://www.izlettin.com/ OSI]-approved open source Dizi izle.


'''4. Derived Works'''
'''4. Derived Works'''
Line 97: Line 97:
The below translations have been offered by members of the community and should be checked for accuracy and possible language problems.  
The below translations have been offered by members of the community and should be checked for accuracy and possible language problems.  


{{:OSHW/translations}}
{{:OSHW/tanawat}}


== Logo repository ==
== Logo repository ==


The open source hardware logo lives at [http://oshwlogo.com oshwlogo.com].
The open source hardware logo lives at [https://www.izlettin.com].


http://i1166.photobucket.com/albums/q601/H3rlihy/OSH_Steellowres.jpg
https://i2.wp.com/www.oshwa.org/wp-content/uploads/2014/03/oshw-logo-800-px.png


== Endorsements ==
== Endorsements ==


OSHW Draft Definition 1.0 has been endorsed by the following persons and/or organization as of {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY}}.
OSHW Draft Definition 1.0 has been endorsed by the following persons and/or organization as of {{TANAWAT}}/{{TANAWAT}}/{{TANAWAT}}.


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.
Line 120: Line 120:
* Adam N. Ward, [http://wardyprojects.blogspot.co.uk/p/open-source-sram-memory-board.html Wardy's Projects]
* Adam N. Ward, [http://wardyprojects.blogspot.co.uk/p/open-source-sram-memory-board.html Wardy's Projects]
* Adam Wolf, [http://www.wayneandlayne.com Wayne and Layne]
* Adam Wolf, [http://www.wayneandlayne.com Wayne and Layne]
* Addie Wagenknecht and Stefan Hechenberger [http://labs.nortd.com/ Nortd Labs]  [http://www.eyebeam.org Eyebeam]  [http://lasersaur.com/ Lasersaur]
* Addie Wagenknecht and Stefan Hechenberger [http://labs.nortd.com/ Nortd Labs]  [http://www.eyebeam.org Eyebeam]  [https://www.izlettin.com/ Lasersaur]
* 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]
* Akiba, [http://www.freaklabs.org/ FreakLabs]
* Akiba, [http://www.freaklabs.org/ FreakLabs]
* 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]
* Alex Glow, [http://hackster.io/glowascii Hackster]
* Alex Hübner, [http://www.la.logicalis.com Logicalis] and [https://sdq.io SDQ.io]
* Alexander Olikevich [http://www.openfablab.org OpenFabLab]
* Alexander Olikevich [http://www.openfablab.org OpenFabLab]
* Alexander Ruiz [http://www.ingeniosolido.com Ingenio Sólido S.A.S]
* Alexander Ruiz [http://www.ingeniosolido.com Ingenio Sólido S.A.S]
Line 134: Line 137:
* Anand Tamboli [http://www.knewron.co.in/ Knewron]
* Anand Tamboli [http://www.knewron.co.in/ Knewron]
* 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]
* 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 140: Line 144:
* Andrew Sliwinski [http://www.omnicorpdetroit.com/ OmniCorpDetroit]
* Andrew Sliwinski [http://www.omnicorpdetroit.com/ OmniCorpDetroit]
* Andrew Stone, [http://www.toastedcircuits.com Toasted Circuits]
* Andrew Stone, [http://www.toastedcircuits.com Toasted Circuits]
* Andy Gelme, [http://hackmelbourne.org Connected Community HackerSpace], Melbourne, Australia and [http://geekscape.org Geekscape Pty. Ltd.]
* Andrew Wenzlaff [http://containrain.com Contain Rain]
* Andy Gelme, [http://hackmelbourne.org Connected Community HackerSpace], Melbourne, Australia and [https://www.izlettin.com.]
* Andy Wickert, [http://www.northernwidget.com Northern Widget LLC]
* Andy Wickert, [http://www.northernwidget.com Northern Widget LLC]
* Anil Kumar Pugalia ([http://profession.sarika-pugs.com Pugs' Passion])
* Anil Kumar Pugalia ([http://profession.sarika-pugs.com Pugs' Passion])
* Anool Mahidharia [http://www.wyolum.com/ WyoLum]
* Anthony Clay, [http://www.zarthcode.com ZarthCode LLC]
* Anthony Clay, [http://www.zarthcode.com ZarthCode LLC]
* Arthur Wolf, [http://smoothieware.org Smoothie]
* Arthur Wolf, [http://smoothieware.org Smoothie]
Line 155: Line 161:
* Bernard Pratz, [http://hackable-devices.org hackable:Devices]
* Bernard Pratz, [http://hackable-devices.org hackable:Devices]
* Bernt Weber, [http://www.splashelec.com/ Splashelec]
* Bernt Weber, [http://www.splashelec.com/ Splashelec]
* Bernardo Tomas, [https://www.erzurumsayfasi.com/ Erzurum Haber]
* Bertrand Le Roy [http://www.nwazet.com Nwazet]
* Bertrand Le Roy [http://www.nwazet.com Nwazet]
* Bhagyashri Sharangpani, [http://www.bhasha.co.cc/ Bhasha Technologies]
* Bhagyashri Sharangpani, [http://www.bhasha.co.cc/ Bhasha Technologies]
* Bill Shaw [http://inanimatereason.com/ Inanimate Reason]
* Bill Shaw [http://inanimatereason.com/ Inanimate Reason]
* Bob Jacobsen [http://jmri.org JMRI]
* Bob Jacobsen [http://jmri.org JMRI]
* Canlı Dizi izle [http://www.diziizlecanli.com/ canlı dizi izle]
* Bob Waldron [http://makerplane.org/ MakerPlane]
* Bob Waldron [http://makerplane.org/ MakerPlane]
* Boseji [http://m8051.blogspot.com Electronics For Bharat]|[http://adharlabs.in A.D.H.A.R Labs]
* Boseji [http://m8051.blogspot.com Electronics For Bharat]|[http://adharlabs.in A.D.H.A.R Labs]
Line 170: Line 178:
* 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]
* Carrie Miller [https://www.waterfiltershq.com/ IoT water filters]
* 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 207: Line 216:
* Deepak Shrivastava
* Deepak Shrivastava
* Demetris Rouslan Zavorotnitsienko [http://www.gizmoforyou.com/ GizmoForYou]
* Demetris Rouslan Zavorotnitsienko [http://www.gizmoforyou.com/ GizmoForYou]
* Derek Elley [https://www.ponoko.com/ Ponoko]
* Diego Spinola [http://www.hackeneering.com/ Hackeneering]
* Diego Spinola [http://www.hackeneering.com/ Hackeneering]
* Dilshan R Jayakody [http://jayakody.info jayakody.info]
* Dilshan R Jayakody [http://jayakody.info jayakody.info]
* Dimitri Albino [http://smartmaker.org smARtMAKER]
* Dimitri Albino [http://smartmaker.org smARtMAKER]
* Dizi izle [http://www.fulldiziizleyelim2.org/ dizi izle]
* D'sun Labs [http://dsunlabs.com/]
* D'sun Labs [http://dsunlabs.com/]
* Dumitru Stama [http://dics.voicecontrol.ro/ dicsEE]
* Dumitru Stama [http://dics.voicecontrol.ro/ dicsEE]
Line 222: Line 233:
* Eric Michaud [http://www.i11industries.com i11 Industries]
* Eric Michaud [http://www.i11industries.com i11 Industries]
* Eric Pan [http://seeedstudio.com/ Seeed Studio]
* Eric Pan [http://seeedstudio.com/ Seeed Studio]
* Antonio [https://www.wellpcb.com/ WellPCB]
* Eric Thompson [http://lowvoltagelabs.com/ Low Voltage Labs]
* Eric Thompson [http://lowvoltagelabs.com/ Low Voltage Labs]
* Ethan Zonca [http://protofusion.org ProtoFusion]
* Ethan Zonca [http://protofusion.org ProtoFusion]
Line 232: Line 244:
* Freddy Deniau
* Freddy Deniau
* Frédéric Jourdan, [http://shop.snootlab.com Snootlab]
* Frédéric Jourdan, [http://shop.snootlab.com Snootlab]
* Fulldiziizlesene [https://www.fulldiziizlesene.net/ Fulldiziizlesene]
* Gabriella Levine, [https://sites.google.com/a/opensailing.net/protei/ Protei], [http://itp.nyu.edu/itp/ ITP]
* Gabriella Levine, [https://sites.google.com/a/opensailing.net/protei/ Protei], [http://itp.nyu.edu/itp/ ITP]
* Gareth Coleman, [http://www.refab-space.org/w/doku.php?id=projects:managed_a_b_switch layer zero labs]
* Gareth Coleman, [http://www.refab-space.org/w/doku.php?id=projects:managed_a_b_switch layer zero labs]
Line 253: Line 266:
* Henrik Denhart [http://denhart.dk Denhart]
* Henrik Denhart [http://denhart.dk Denhart]
* Hong Phuc Dang [http://fossasia.org/ FOSSASIA]
* Hong Phuc Dang [http://fossasia.org/ FOSSASIA]
* Hong Phuc Dang [https://www.izlettin.com videoizle]
* Hristian Daskalov [http://opensourceuni.org/ The Open Source University]
* Ian Daniher, [http://nonolithlabs.com Nonolith Labs]
* Ian Daniher, [http://nonolithlabs.com Nonolith Labs]
* Ian Lee [http://blog.ianlee.info Software & Sawdust]
* Ian Lee [http://blog.ianlee.info Software & Sawdust]
* Ivan Jorge Boesing, [http://www.brfirst.org FIRST Brazil]
* Ivan Jorge Boesing, [http://www.brfirst.org FIRST Brazil]
* J. Simmons [http://mach30.org/ Mach 30: Foundation for Space Development]
* J. Simmons [http://mach30.org/ Mach 30: Foundation for Space Development]
* Jaco du Plessis [http://www.hbnet.co.za hbnet Private Internet Services]
* Jakub Kákona, [http://www.mlab.cz MLAB] [http://www.ust.cz UST]
* Jakub Kákona, [http://www.mlab.cz MLAB] [http://www.ust.cz UST]
* James Adams, [http://www.makenub.com/ MakeNub]
* James Adams, [http://www.makenub.com/ MakeNub]
Line 265: Line 281:
* Jason Huggins [http://bitbeam.org Bitbeam]
* Jason Huggins [http://bitbeam.org Bitbeam]
* Jason Veneman, [http://intelligenate.com Intelligenate]
* Jason Veneman, [http://intelligenate.com Intelligenate]
* Adam Mayer, [https://canlidiziizlesene.com/ Canlidiziizlesene]
* Jatinderjit Singh, [http://www.embisys.com Embisys]
* Jatinderjit Singh, [http://www.embisys.com Embisys]
* Jayson Tautic, [http://www.tautic.com TAUTIC ELECTRONICS LLC]
* Jayson Tautic, [http://www.tautic.com TAUTIC ELECTRONICS LLC]
Line 275: Line 292:
* Jeffrey Antony, [http://jeffrey.co.in Jeffrey's Personal Website]
* Jeffrey Antony, [http://jeffrey.co.in Jeffrey's Personal Website]
* Jeremy Blum, [http://www.jeremyblum.com/ JeremyBlum.com] [http://www.creativemachines.org Cornell University Creative Machines Lab]
* Jeremy Blum, [http://www.jeremyblum.com/ JeremyBlum.com] [http://www.creativemachines.org Cornell University Creative Machines Lab]
* Jeremy Elson, [https://www.lectrobox.com Lectrobox]
* Jeremy Saglimbeni, [http://thecustomgeek.com/ thecustomgeek.com]
* Jeremy Saglimbeni, [http://thecustomgeek.com/ thecustomgeek.com]
* Jim Barkley, [http://www.mitre.org/ The MITRE Corporation]
* Jim Barkley, [http://www.mitre.org/ The MITRE Corporation]
* Jimmie P. Rodgers [http://jimmieprodgers.com/ JimmiePRodgers.com]
* Jimmie P. Rodgers [http://jimmieprodgers.com/ JimmiePRodgers.com]
* Jinbuhm Kim [http://www.wiznettechnology.com/ WIZnet]
* Jinbuhm Kim (김진범) [http://ateamventures.com/ ATEAM VENTURES]
* Joan Espinoza [http://www.pinguino.org.ve PingüinoVE]
* Joan Espinoza [http://www.pinguino.org.ve PingüinoVE]
* Joel Murphy [http://www.rachelselectronics.com/ Rachel's Electronics] [http://www.newschool.edu/parsons/mfa-design-technology/ Parsons D+T]
* Joel Murphy [http://www.rachelselectronics.com/ Rachel's Electronics] [http://www.newschool.edu/parsons/mfa-design-technology/ Parsons D+T]
Line 287: Line 305:
* Johnny Russell [http://ultimachine.com/ UltiMachine]
* Johnny Russell [http://ultimachine.com/ UltiMachine]
* Jon Kuniholm, [http://openprosthetics.ning.com/ The Open Prosthetics Project]
* Jon Kuniholm, [http://openprosthetics.ning.com/ The Open Prosthetics Project]
* Bilgi Sitesi [https://www.hergunyenibilgi.com/ Bilgi Sitesi]
* Jon Masters [http://www.jonmasters.org/ www.jonmasters.org]
* Jon Masters [http://www.jonmasters.org/ www.jonmasters.org]
* Jonathan Dahan, [http://www.islandlabs.org/ Island Labs]
* Jonathan Dahan, [http://www.islandlabs.org/ Island Labs]
Line 319: Line 338:
* 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]
* Mike Dong [https://www.pcbgogo.com/ PCBGOGO]
* 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]
Line 324: Line 344:
* 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 A. Cooper, [http://smoothieware.org/ Smoothie]
* Mark McComb, [http://www.hacktronics.com/ hacktronics]
* Mark McComb, [http://www.hacktronics.com/ hacktronics]
* Mark Wolf, [https://www.maleetronic.com/ Maleetronic]
* 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 345: Line 368:
* Moritz von Buttlar [http://www.opensource-solar.org/ Opensource-Solar]
* Moritz von Buttlar [http://www.opensource-solar.org/ Opensource-Solar]
* Morten I. Larsen
* Morten I. Larsen
* Naoufel Razouane [http://www.facebook.com/pages/FLVM-Tunisie-Tunisia-DIY-%D8%AA%D9%88%D9%86%D8%B3-%D8%A5%D8%B0%D9%86/167757549921914 Tunisia-DIY]
* Muzhichkov Alexander [http://www.eliving.space eliving.space]
* Naoufel Razouane [http://openfab.tn OpenFab Tunisia]
* Nathan Seidle [http://www.sparkfun.com SparkFun Electronics]
* Nathan Seidle [http://www.sparkfun.com SparkFun Electronics]
* Nicholas C Lewis [http://reprapbreeding.blogspot.com/ A RepRap Breeding Program]
* Nicholas C Lewis [http://reprapbreeding.blogspot.com/ A RepRap Breeding Program]
Line 355: Line 379:
* 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]
* 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]
* Partha Pratim Ray [https://www.sikkimuniversity.ac.in/index.php?option=com_content&view=article&id=489&Itemid=603 Sikkim University]
* Patrick Korkuch
* Patrick Korkuch
* Patrick Lloyd
* Patrick Lloyd
Line 366: Line 392:
* Phillip Torrone, [http://www.makezine.com/ MAKE magazine] [http://www.adafruit.com/ Adafruit Industries]
* Phillip Torrone, [http://www.makezine.com/ MAKE magazine] [http://www.adafruit.com/ Adafruit Industries]
* Pierce Nichols [http://logos-electro.com Logos Electromechanical LLC]
* Pierce Nichols [http://logos-electro.com Logos Electromechanical LLC]
* Pierre Padilla [http://biomakerslab.wixsite.com/home] Biomakers Lab
* 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]
* 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]  
* Raf Wawer [http://www.ancientcrafts.org Ancient Crafts and Arts Society]
* Raf Wawer [http://www.ancientcrafts.org Ancient Crafts and Arts Society]
Line 376: Line 404:
* Raúl Oviedo [http://ayudaelectronica.com/ Ingenieria Electronica]
* Raúl Oviedo [http://ayudaelectronica.com/ Ingenieria Electronica]
* Ravichandra Seveelavanan [http://www.LZRDM.org/ LZRDM]
* Ravichandra Seveelavanan [http://www.LZRDM.org/ LZRDM]
* Rebika Rai [https://www.sikkimuniversity.ac.in/index.php?option=com_content&view=article&id=449&Itemid=592 Sikkim University]
* 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]
* Robert Fitzsimons [http://partfusion.com/ Part Fusion Electronics]
* Robert Fitzsimons [http://partfusion.com/ Part Fusion Electronics]
Line 391: Line 421:
* Shannon Morrisey
* Shannon Morrisey
* Shigeru Kobayashi [http://www.iamas.ac.jp/E/index.html IAMAS] [http://funnel.cc Funnel] [http://gainer.cc Gainer]
* Shigeru Kobayashi [http://www.iamas.ac.jp/E/index.html IAMAS] [http://funnel.cc Funnel] [http://gainer.cc Gainer]
* Simon Gao [https://www.pcbway.com/ PCBWay]
* Simon Gao [https://www.pcbastore.com/ pcbastore]
* Simone Marzulli [http://onioncoding.altervista.org Onioncoding]
* Simone Marzulli [http://onioncoding.altervista.org Onioncoding]
* 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]
Line 407: Line 439:
* Tomasz Mloduchowski [http://www.xlogic.pl XLogic] [http://blattaria.co.uk Blattaria, Ltd.]
* Tomasz Mloduchowski [http://www.xlogic.pl XLogic] [http://blattaria.co.uk Blattaria, Ltd.]
* Troy Dowling [http://www.troydowling.org TroyDowling.org]
* Troy Dowling [http://www.troydowling.org TroyDowling.org]
* Tsvetan Usunov [https://www.olimex.com Olimex.com]
* Tully Gehan, [http://samuraicircuits.com/ Samurai Circuits]
* Tully Gehan, [http://samuraicircuits.com/ Samurai Circuits]
* Tuomo Tammenpää, [http://www.ohanda.org/ OHANDA - Open Source Hardware and Design Alliance]
* Tuomo Tammenpää, [http://www.ohanda.org/ OHANDA - Open Source Hardware and Design Alliance]
Line 420: Line 453:
* 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]
* Yoonseok Pyo, [http://www.robotis.com/ ROBOTIS]
* Zhang Dong,[http://www.homemode.me HOMEMODE]
* Chris Liu, [http://www.oshw.com oshw.com]
* Michelle Fu [https://www.ourpcb.com ourpcb.com]
* Amyfu [http://www.customwiringloom.com customwiringloom.com]
* Yannick Roels [http://www.cultureghem.be/ cultureghem]
* Austin Clinton [https://www.wiringo.com wiringo.com]
* Felix Law [https://www.allchips.ai Allchips.ai]
* Bean zheng [http://www.pcbgogo.com/y PCBA Turnkey Service]
* Leo Chen [https://www.lhd-pcb.com/ LHD PCB]
* Kofi Lew, [https://buddydiy.com BuddyDIY]
*Mr Zhou, [https://www.freewingmodel.net Freewing Model]

Revision as of 19:11, 14 October 2019

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

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

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

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 Dizi izle.

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.

OSHW/tanawat

Logo repository

The open source hardware logo lives at [4].

oshw-logo-800-px.png

Endorsements

OSHW Draft Definition 1.0 has been endorsed by the following persons and/or organization as of Template:TANAWAT/Template:TANAWAT/Template:TANAWAT.

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