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 FAQ
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 17: | Line 17: | ||
"Let us stand on each other’s shoulders, not each other’s toes." --Tiny BASIC developer Dennis Allison, 1975 | "Let us stand on each other’s shoulders, not each other’s toes." --Tiny BASIC developer Dennis Allison, 1975 | ||
=== What files | === What files should I share? === | ||
You should share all the files needed to build *and* modify your hardware. As the [[OSHW | open-source hardware definition]] explains, that means the version of the files that you would prefer for making changes to the design, not an intermediate or obfuscated version. For mechanical stuff, this means the original CAD files. For circuit boards, it's the original schematic and board layout files. | |||
Unfortunately, the original design files for hardware are often in proprietary formats for expensive software tools. In this case, it's helpful and encouraged to also offer versions of the design in alternative or intermediate formats that can be viewed or edited with common or free programs. For example, PDFs of circuit schematics, Gerbers for circuit board layouts, and IGES or STL files for mechanical objects. These allow people without access to expensive or proprietary software to make at least some use of your design. Please note, however, that this is not a substitute for releasing the original files - the core of open-source hardware practice. | Unfortunately, the original design files for hardware are often in proprietary formats for expensive software tools. In this case, it's helpful and encouraged to also offer versions of the design in alternative or intermediate formats that can be viewed or edited with common or free programs. For example, PDFs of circuit schematics, Gerbers for circuit board layouts, and IGES or STL files for mechanical objects. These allow people without access to expensive or proprietary software to make at least some use of your design. Please note, however, that this is not a substitute for releasing the original files - the core of open-source hardware practice. | ||
=== What are other best practices for open source hardware? === | === What are other best practices for open source hardware? === | ||
Line 34: | Line 34: | ||
=== Won't people rip me off? === | === Won't people rip me off? === | ||
People will rip you off in the sense that they will use your designs as the basis for more advanced designs. If you don't want that to happen, you should probably not call your hardware "open source." | |||
Those of us who do build open source hardware want people to build on our designs, or at least think the benefits of the situation are worth the competition. | |||
=== Why aren't non-commercial restrictions compatible with open source hardware? === | === Why aren't non-commercial restrictions compatible with open source hardware? === | ||
Line 49: | Line 45: | ||
In particular, because making hardware invariably involves money, it's very difficult to make use of a hardware design without involving some commercial activity. For example, say a group of friends wanted to get together and order ten copies of a hardware design - something that's often much cheaper than each person ordering their own copy. If one person places the order and the others pay him back for their share, they'd probably be violating a non-commercial restriction. Or say someone wants to charge people to take a workshop in which they make and keep a copy of your hardware design - that's also commercial activity. In general, there are just very few ways for someone to use a hardware design without involving some sort of commercial activity. | In particular, because making hardware invariably involves money, it's very difficult to make use of a hardware design without involving some commercial activity. For example, say a group of friends wanted to get together and order ten copies of a hardware design - something that's often much cheaper than each person ordering their own copy. If one person places the order and the others pay him back for their share, they'd probably be violating a non-commercial restriction. Or say someone wants to charge people to take a workshop in which they make and keep a copy of your hardware design - that's also commercial activity. In general, there are just very few ways for someone to use a hardware design without involving some sort of commercial activity. | ||
=== Who makes open source hardware? === | |||
=== How to ensure that all modifications to my projects are put back into open source? === | === How to ensure that all modifications to my projects are put back into open source? === | ||
=== Links === | === Links === |