Dan Maloney
Awesome
@Frank Buss that is what we are aiming for with the certification. We have had times where we certified something and someone from the community came back and said that the documentation was not enough to reproduce it. Once we confirmed that we gave the original creator a choice: update the documentation or become decertified. We all worked together to improve the documentation so that it was better for users
@Frank Buss even then, you still need hardware capable of running the GPL software. I feel the reasonable demands are there. If there are further reasonable demands, please share the thought.
@Leon Anavi One of the Bulgarian kings of open source hardware!
@Michael Weinberg sounds good, but maybe it should be a requirement on the definition page
:-D
@Michael Weinberg hehe :) Olimex are the local open source hardware kings here :)
@Michael Weinberg definitely! And I'm thinking more about products that are mostly a circuit board, which don't have a ton of secret sauce once all files and BOM are released, and which take zero effort to reproduce. Single digit effort is fine, I'm just thinking of something > 0.
@Frank Buss "would be nice if the license would require any information to reproduce it yourself, as GPL does for software" -> Please, no hand-holding for the masses. There are limits for what can be done for design documentation vs not allowing shroud around certain design aspects of supposedly 'open' stuff.
@Frank Buss the question is how deep do you need to go? Do you need recipes for making your own transistors?
digikey part number would be sufficient :-)
@Frank Buss how about radioshack part number?
ok, manufacturer part number might be the best solution, then you can find it with http://findchips.com etc.
digikey doesn't have most parts I use
@Frank Buss the certification requires you to comply with the definition, and the definition requires documentation. But, again, it is hard to create detailed rules that can be easily applied to kite surfers, violins, and microcontroller boards
@Michael Weinberg @Drew Fustini btw it will be nice to have a ranking by countries at https://certification.oshwa.org/list.html. I guess Bulgaria at the moment is on the top of the list for Europe :)
That is where the feedback from the community really helps. They are the best positioned to know hen things are "good eough"
@Leon Anavi I can tell you with a high degree of confidence that Bulgaria has the highest per-capita certification of any country. We are working on a project that could result in an interactive map and leader board
@Frank Buss "digikey part number would be sufficient" -> No. Here is the schematic with general component IDs, here is the PCB layout, here is the source code, here is the gist of the mechanical interface, now be a cool dudette or dude and build it.
@Michael Weinberg actually, all projects certified from Bulgaria are from my hometown - Plovdiv :)
I am trying to convince people from other places in Bulgaria to certify their products.
OK folks, here we are the end of another information-packed hour. You never know which way a Hack Chat is going to go, and this one took off on its own trajectory from the start. Really useful info, though - so many dimensions to IP and licensing.
I'm going to call official time, but the OSHWA people - think I saw @Drew Fustini on, hi Drew! - can keep fielding questions as long as they want to. I'll just say a big thanks to @Michael Weinberg and everyone else for coming in on short notice to celebrate Open Hardware Month!
@Leon Anavi in that case Ploviv has the highest per-capital certification of any city on earth
@Michael Weinberg I have a project that I publish all the hardware. For software I am a little worried. I want it to be open so people can make improvements but I would like to verify it because if it sons work It can destroy the hardware and whatever project is connected to it. Whats the best way to approach this
(https://hackaday.io/project/164913-open-power)
Thanks @Michael Weinberg
Thank you
@Brian I'm just a programmer, can't figure it out myself
Remember I'll be posting a transcript at https://hackaday.io/event/168042-open-hardware-month-hack-chat within the next hour or so. And don't forget to come along next week for a SatNOGS update:
@John Loefler clear documentation is probably a better tool than a license to control that kind of thing. Laws can't fix everything!
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.