<div dir="ltr">wow.</div><div class="gmail_extra"><br clear="all"><div>_________________________________________<br>malcolm stanley<br><br>google.voice: 215.821.6252 <div>Cell: 267.251.9479 <------------- new<br>
email: <a href="mailto:a.malcolm.stanley@gmail.com" target="_blank">a.malcolm.stanley@gmail.com</a><br>twitter / linkedin: amstanley<br>Read my blog at <a href="http://soaringhorse.blogspot.com" target="_blank">http://soaringhorse.blogspot.com</a><br>
_________________________________________</div></div>
<br><br><div class="gmail_quote">On Thu, Mar 7, 2013 at 12:04 PM, Catarina Mota <span dir="ltr"><<a href="mailto:catarina@openmaterials.org" target="_blank">catarina@openmaterials.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi all,</div><div><br></div><div>We're organizing a hackathon to arrive at some OSHW documentation best practices and tools: <a href="http://www.opensourcewarehouse.org/" target="_blank">http://www.opensourcewarehouse.org</a></div>
<div><br></div>It all started a few months ago with a few causal conversations with open source hardware developers that were concerned with the fact that weren't getting enough public contributions to their projects and also that they sometimes found it difficult to build on top of other's projects. Both were related to insufficient, deficient or hard to interpret documentation. So this got us thinking about how can we improve documentation to make open source hardware more accessible to all and to drive more contributions to projects. This is the initial list of challenges we identified (to build upon by the community): <a href="http://www.opensourcewarehouse.org/problem-statement/" target="_blank">http://www.opensourcewarehouse.org/problem-statement/</a><div>
<br></div><div>And here's an initial taxonomy (to be refined or abandoned at the hackathon): <a href="https://docs.google.com/spreadsheet/ccc?key=0AkNG-lv1ELQvdHViNEdtVHp4dHRWOU8tcDNSbXROY3c&usp=sharing" target="_blank">https://docs.google.com/spreadsheet/ccc?key=0AkNG-lv1ELQvdHViNEdtVHp4dHRWOU8tcDNSbXROY3c&usp=sharing</a><br>
<div><br></div><div>Since this a huge challenge and one that concerns the entire community, we figured the best way to approach it would be to start with a hackathon to identify the problems and find ways to tackle them.</div>
<div><br></div><div>We hope that some of the outcomes will be:</div><div><br></div><div>- A set of best practices for open source hardware documentation, including a taxonomy and a check list.</div><div>- A set of recommended software tools for generating and sharing documentation - this may either be the adoption of something that is already out there or, more likely, a mashup of existing platforms</div>
<div>- A way to identify which parts of a project are open source and have documentation</div><div>- The seed for an OSHW repository or a search engine</div><div><br></div><div>I hope many of you can join us and bring your ideas and insights to the table. More details coming up on a separate email.</div>
<div><br></div><div>Cheers,</div><div>Catarina</div></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote">On Tue, Mar 5, 2013 at 4:17 PM, Windell H. Oskay <span dir="ltr"><<a href="mailto:windell@oskay.net" target="_blank">windell@oskay.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br>
On Mar 3, 2013, at 5:35 PM, David A. Mellis <<a href="mailto:dam@mellis.org" target="_blank">dam@mellis.org</a>> wrote:<br>
<br>
> Hey all,<br>
><br>
> I copied Nate's best practices document (<a href="http://www.oshwa.org/sharing-best-practices/" target="_blank">http://www.oshwa.org/sharing-best-practices/</a>) into a Google Doc: <a href="https://docs.google.com/document/d/1CiL9nd0xPOGRkHcNnOTZdHG-niAHteOm74f9PmAHdLg/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1CiL9nd0xPOGRkHcNnOTZdHG-niAHteOm74f9PmAHdLg/edit?usp=sharing</a><br>
><br>
> Please help improve it.<br>
<br>
</div></div>I have made some significant edits to the document in a few sections:<br>
"Original Design Files," "Auxiliary Design Files," and some parts of "Additional Notes on Best Practice for OSHW" at the end.<br>
<br>
I hope that these edits are considered helpful.<br>
<br>
<br>
I still see a lot of room for improvement remaining, if anyone else would like to help out, in the following sections:<br>
<br>
* The intro to "Sharing Files"<br>
* Bill of materials<br>
* Software and Firmware -- could really be expanded a lot<br>
* Photos<br>
* Instructions<br>
* Legal practices to protect sharing<br>
* Distributing Hardware<br>
* Additional notes<br>
<br>
<br>
<br>
Windell H. Oskay, Ph.D.<br>
Co-Founder and Chief Scientist<br>
Evil Mad Scientist Laboratories<br>
175 San Lazaro Ave, STE 150<br>
Sunnyvale CA 94086<br>
<a href="http://www.evilmadscientist.com/" target="_blank">http://www.evilmadscientist.com/</a><br>
<div><div><br>
_______________________________________________<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" target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<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" target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
<br></blockquote></div><br></div>