we make and sell open source hardware for a living, we do not thing the tools matter. so far no one else who does OSHW thinks it matters either, that said - we pretty much all have the goal to move to OSS tools and file formats. we all seem to know it's not going to happen overnight.smindinvern wrote:I'm guessing that you're referring strictly to the use of Eagle in OSHW designs, but more generally speaking, I don't think it takes much to show that that statement is completely false. A design that's released in altium designer will do little to no good for hobbyists. So yes, it follows the OSHW license, but does it really follow the spirit of open source? Well, I think that's a matter of opinion.
if the designer only uses a certain tool but does everything reasonable for someone else to re-make the design, that's within the spirit of OSHW.
if you can provide an example of someone purposefully using an format that no one can use and no one can re-make based on what they released, and they're calling it OSHW please post it (we are not aware of a single example).
if a design is released in altium that's not ideal, but as long as it's possible to make / re-make, it really doesn't matter. eventually the maker will just save the design file to an open file format from their tool of choice. it's like caring about using windows to make OSHW. it doesn't matter, but ideally we'll all have a good assortment of OSS tools and file formats.
please review the OSHW definition, we all spent a lot of time talking about this
http://www.openhardwaresummit.org/oshw-definition-v1-0/
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).