<div dir="ltr">Come after "YOU" - the YOU refers to people who drew up the OSHWA standard?<div><br></div><div>Marcin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 22, 2016 at 1:44 PM, lkcl . <span dir="ltr"><<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Aug 22, 2016 at 7:16 PM, Marcin Jakubowski<br>
<<a href="mailto:marcin@opensourceecology.org">marcin@opensourceecology.org</a>> wrote:<br>
<br>
> Thanks, good points of clarification.<br>
<br>
</span> no problem, man. ah! i got a _great_ example. it's very simple:<br>
you know how a "lobster pot" is open? :)<br>
<br>
that's what "open source" is. it's an insidious trap from which<br>
there's no escape once you're in. by contrast, "libre" provides a<br>
*guarantee* that you can "escape the lobster pot" (which is why the<br>
FSF and many people were extremely pissed off with the purism "librem"<br>
laptop).<br>
<br>
now, that's not to say that the OSHWA's documentation are not an<br>
extremely good and extremely necessary idea: the similarities to what<br>
i learned from developing the EOMA hardware standards is startling.<br>
<br>
here's the key differences:<br>
<br>
(1) through the tough lessons of the past five years in developing the<br>
EOMA68 standards, i had people actually try to take control of it for<br>
their own purposes, making statements that they were NOT AUTHORISED to<br>
make, bringing the standard into disrepute and, by making promises of<br>
changes that would make it ambiguous instead of a guaranteed, trusted<br>
simple upgrade path, actually risked destroying the standard in its<br>
entirety. i had to take them to task, it wasn't fun, but it was<br>
important to do so.<br>
<br>
(2) i've *actually developed* hardware based on the standard, and<br>
have adapted the standard accordingly. so i've had opportunities for<br>
feedback to check its integrity. it's really really important (as the<br>
dog's dinner known as the 96boards standard shows) *not* to finalise a<br>
standard until you've been through some iterations and got some *real*<br>
feedback.<br>
<br>
(3) Certification Marks (the "standards" equivalent of "Trademarks")<br>
are really *really* important. by the very fact that the OSHWA<br>
document exists, there is *already* a Certification Mark on it... it's<br>
just an "unregistered" one. once the issues with the use of the words<br>
"open source" are fixed i strongly recommend getting a "registered"<br>
Certification Mark.<br>
<br>
(4) nowhere in the OSHWA document do i see the (very real)<br>
possibility described or covered of people being harmed (or killed) by<br>
people who implement (so badly that it causes death or injury) an<br>
OSHWA Certified product. this is *unbelievably* important to cover as<br>
part of the Certification process. the problem for the creators of<br>
the OSHWA document will be if they *don't* have a procedure in place<br>
to deal with this unfortunate eventuality, as the family and/or estate<br>
of anybody who is killed by an OSHWA-Cerfified product, rather than go<br>
after the individuals who used the Certification blithely and with<br>
blatant disregard for human life, they'll come after YOU instead. yes<br>
these things really do need to be discussed and taken into<br>
consideration.<br>
<div class="HOEnZb"><div class="h5"><br>
l.<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b style="font-size:12.8px">Full Disclosure Agreement:</b><span style="font-size:12.8px"> OSE works openly. All conversations in this email are intended to be transparent and subject to sharing, with due respect. OSE does not sign NDAs in order to promote collaboration. All of our work is libre or open source. If you are discussing potential development collaboration, your work must also be open source pursuant to the Open Source Hardware Association </span><a href="http://www.oshwa.org/definition/" style="font-size:12.8px" target="_blank">definition</a><span style="font-size:12.8px">. </span><br></div><div><br></div><div>See Global Village Construction Set <a href="http://www.ted.com/talks/marcin_jakubowski" target="_blank">TED Talk</a>. Sign up for our <a href="http://opensourceecology.org/wiki/OSE_Design_Sprint" target="_blank">Design Sprints</a>. Subscribe as a <a href="http://opensourceecology.org/community/#truefans" target="_blank">True Fan</a>. <span style="font-size:13px">See <a href="https://www.tsu.co/OpenSourceEcology" target="_blank">Tsu</a> or </span><a href="https://www.facebook.com/OpenSourceEcology" style="font-size:13px;color:rgb(17,85,204)" target="_blank">Facebook</a><span style="font-size:small;font-family:arial"> for updates</span><span style="font-size:13px">. Subscribe to monthly update <a href="http://opensourceecology.org/wiki/OSEmail" target="_blank">OSEmail</a>. Donate to our <a href="http://opensourceecology.org/wiki/Other_donation_options" target="_blank">501(c)3</a>.</span></div><div><br></div><span style="font-family:arial;font-size:small">Marcin Jakubowski, Ph.D.</span></div><div dir="ltr"><span style="font-family:arial;font-size:small">Executive Director</span><div style="font-family:arial;font-size:small">Open Source Ecology</div><div style="font-family:arial;font-size:small"><a href="http://opensourceecology.org/" style="color:rgb(17,85,204)" target="_blank">http://opensourceecology.org</a></div><div style="font-family:arial;font-size:small"><br></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>