<p>See <a href="http://www.SENSORICA.co">www.SENSORICA.co</a> for open innovation and peer production models. <br>
Within SENSORICA we have the habit of publishing not only the final design files but and the working documents wlthat leat to that design, exposing past mistakes and their solutions, possible pitfalls, decision making processes, etc.<br>
>From my 6 years experience developing open hardware in an Open Value Network environment I can say that it happens very often that someone tries to make an improvement to something and goes where others have failed in the past. Documenting the path to the final design has huge value.<br>
</p>
<div class="gmail_quote">On Aug 17, 2016 12:07 PM, "Jay Patel" <<a href="mailto:rockworldmi@gmail.com">rockworldmi@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">is OpenBSD more compatible with OSHWA project?<div> <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 16, 2016 at 9:46 PM, Matt Maier <span dir="ltr"><<a href="mailto:blueback09@gmail.com" target="_blank">blueback09@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">In terms of a structured way to capture all of the documentation you describe, this is a process I demonstrated a while back for Open Source Ecology's LifeTrac tractor <a href="http://opensourceecology.org/wiki/Distributed_Collaboration" target="_blank">http://opensourceecolo<wbr>gy.org/wiki/Distributed_<wbr>Collaboration</a><div><br></div><div>I'm working on a better way <a href="http://github.howstr.com/" target="_blank">http://github.howstr.com/</a></div><div><br></div><div>Your write up is pretty good. You should add a section about keeping the documentation up to date as the project evolves. It also kind of highlights the reason open source hardware documentation is so scant...it's a lot of work and it's not clear to many what they get back for doing all that work.</div><div><br></div><div>We need to make it easier, so that it's not so much work.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Fri, Jul 22, 2016 at 10:31 AM, Bonvoisin, Jeremy <span dir="ltr"><<a href="mailto:jeremy.bonvoisin@tu-berlin.de" target="_blank">jeremy.bonvoisin@tu-berlin.de</a><wbr>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div lang="EN-GB" link="blue" vlink="purple">
<div>
<p class="MsoNormal">Hi, <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">I’m a researcher at the Technical University Berlin where we have a newly started
<a href="http://130.149.46.183/wiki/index.php/OPEN!_Methods_and_tools_for_community-based_product_development" target="_blank">
French-German research project on open source hardware</a>. <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">I would like to share with you a document we made to summarize the best practices we observed through the analysis of a large number of open source hardware projects. The page is named “<a href="http://130.149.46.183/wiki/index.php/A_guide_to_Open_Source_Hardware" target="_blank">a
guide to open source hardware</a>” and attempts giving practical guidance regarding documentation of open source hardware products, especially for mechanic products. This is some sort of extension of the “<a href="http://www.oshwa.org/sharing-best-practices/" target="_blank">Best
Practices of Open Source Hardware 1.0</a>” of the OSHWA.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I would be glad to get your impressions, feedback, critics or even propositions for further development of this document.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I am also open for merging this document with existing initiatives, for example if there are discussions about a second version of the “best practices” of the OSHWA.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks in advance for your reactions!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards, <u></u><u></u></p>
<p class="MsoNormal">Jérémy Bonvoisin<u></u><u></u></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f">Dr. </span>
<span lang="DE" style="font-size:10.0pt;color:#943634">Jérémy Bonvoisin</span><span lang="DE"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f">Ingénieur esiea – Research engineer</span><span lang="DE"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f">Institut für Werkzeugmaschinen und Fabrikbetrieb - IWF</span><span lang="DE"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f">Fachgebiet Industrielle Informationstechnik</span><span lang="DE"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="DE" style="font-size:10.0pt;color:#7f7f7f">Technische Universität Berlin</span><span lang="DE"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;color:#7f7f7f">Mail:
<a href="mailto:jeremy.bonvoisin@tu-berlin.de" target="_blank">jeremy.bonvoisin@tu-berlin.de</a></span><span lang="FR"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;color:#7f7f7f">Tel.:
</span><span lang="DE" style="font-size:10.0pt;color:#7f7f7f"><a href="tel:%2B49%20%280%2930%2039006%20358" target="_blank"><span lang="FR">+49 (0)30 39006 358</span></a></span><span lang="FR"><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="FR" style="font-size:10.0pt;color:#7f7f7f">Raum: PTZ 563</span><span lang="FR"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br></div></div><span>______________________________<wbr>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a><br>
<a href="http://lists.oshwa.org/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.oshwa.org/listinf<wbr>o/discuss</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a><br>
<a href="http://lists.oshwa.org/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.oshwa.org/listinf<wbr>o/discuss</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a><br>
<a href="http://lists.oshwa.org/listinfo/discuss" rel="noreferrer" target="_blank">http://lists.oshwa.org/<wbr>listinfo/discuss</a><br>
<br></blockquote></div>