<p>Interesting thoughts. We have similar discussions at my own startup about potentially strategic releases of stuff we write or design. I personally come down on the side of total radical openness. I think everything <a href="http://should.be">should.be</a> built and designed and documented entirely publically from the beginning. I personally think ANY effort to "avoid" clones is against the whole concept of open sourcing information.</p>
<p>Of course lots of other people have different thoughts. :)</p>
<div class="gmail_quote">On May 9, 2015 10:09 AM, "Pierce Nichols" <<a href="mailto:pierce@logos-electro.com">pierce@logos-electro.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">Creators crowdfunding new OSHW products have a good reason to keep the files private until they are shipping; they'd typically like to ship their product before any clones. <div><br></div><div>I think there's an opportunity here for the OSHWA to both help with this issue and have the opportunity to enforce best practices. The OSHWA could create a file escrow system for crowdfunders. It ought to work something like this:</div><div><br></div><div>-- Developer deposits files with OSHWA and pays a fee</div><div>-- OSHWA audits the files to make sure they meet the definition</div><div>-- If they do, the developer gets a badge or something to show that they aren't going to forget to release the files or anything like that</div><div>-- Once the product starts shipping and/or a set time period passes, OSHWA publishes the files.</div><div><br></div><div>Thoughts?</div><div><br></div><div>-p</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 6:03 PM, Emilio Velis <span dir="ltr"><<a href="mailto:contacto@emiliovelis.com" target="_blank">contacto@emiliovelis.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"><div>This could be one of the points to think about regarding "best practices", to actually release files before claiming to be open source or to support it.<br><br></div>This could be a very healthy position that the whole open source community should enforce.<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 8 May 2015 at 17:10, Drew Fustini <span dir="ltr"><<a href="mailto:pdp7pdp7@gmail.com" target="_blank">pdp7pdp7@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">Yes, that is a very good point.<br><br>I did get to meet them last month when I was out in California for a conf. They seem sincere about open source, but I agree, the proof is in the publishing of properly licensed files.<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 4:41 PM, Ben Gray <span dir="ltr"><<a href="mailto:ben@phenoptix.com" target="_blank">ben@phenoptix.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">Things that say they will be open source don't always become open source. To say something "is totally open source" and then not have the files available is in my opinion dishonest. </div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr">--<br><br>Best Regards<br><br>Ben Gray - Director<div><br><img src="http://images.phenoptix.com/forum/AVRISP/logo.png" height="54" width="200"><br><br><a href="http://www.phenoptix.com" target="_blank">www.phenoptix.com</a><br><a href="http://twitter.com/phenoptix" target="_blank">twitter.com/phenoptix</a></div><div><a href="http://plus.google.com/+phenoptix" target="_blank">plus.google.com/+phenoptix</a><br></div><div><br></div><div><br><br><br><br></div></div></div></div>
<br><div class="gmail_quote"><div><div>On 8 May 2015 at 20:58, Drew Fustini <span dir="ltr"><<a href="mailto:pdp7pdp7@gmail.com" target="_blank">pdp7pdp7@gmail.com</a>></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>I thought this would be of interest. inexpensive, open source and<br>
powerful enough for several use cases. i backed it yesterday, and<br>
hope that Next Thing Co. can execute on time and on budget:<br>
<br>
Next Thing Co. Releases “World’s First” $9 Computer<br>
<a href="http://makezine.com/2015/05/07/next-thing-co-releases-worlds-first-9-computer/" target="_blank">http://makezine.com/2015/05/07/next-thing-co-releases-worlds-first-9-computer/</a><br>
<br>
"The board is Open Hardware, runs a flavor of Debian Linux, and boasts<br>
a 1Ghz R8 ARM processor, 512MB of RAM, and 4GB of eMMC storage. It is<br>
more powerful than a Raspberry Pi B+ and equal to the BeagleBone Black<br>
in clock speed, RAM, and storage. Differentiating Chip from Beagle is<br>
its built-in WiFi, Bluetooth, and the ease in which it can be made<br>
portable, thanks to circuitry that handles battery operation."<br>
<br>
For the Kickstarter page:<br>
<a href="https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer" target="_blank">https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer</a><br>
<br>
"We built C.H.I.P. to make tiny powerful computers more accessible and<br>
easier to use. A huge part of making C.H.I.P. accessible is making<br>
sure that it can change to meet the needs of the community. That's why<br>
both C.H.I.P. and PocketC.H.I.P. are both TOTALLY OPEN SOURCE. This<br>
means all hardware design files schematic, PCB layout and bill of<br>
materials are free for you the community to download, modify and use."<br>
<br>
<br>
cheers,<br>
drew<br></div></div>
_______________________________________________<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>
</blockquote></div><br></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>
<br></blockquote></div><br></div>
</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>
<br></blockquote></div><br></div>
</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>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Pierce Nichols<br>Principal Engineer<br>Logos Electromechanical, LLC<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>