<div dir="ltr">Although I like the idea of an index, it seems to be enough of a problem (even on this list) to recognise what constitutes Open Source Hardware or not. I feel that adding an index or score could muddy the waters even more.<div>However it could add to understanding if the compliance elements are stressed and failure underlined rather than a low score given.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br><br>Best Regards<br><br>Ben Gray - Director<div><br><img src="http://images.phenoptix.com/forum/AVRISP/logo.png" width="200" height="54"><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">On 25 February 2015 at 07:16, Jeffrey Warren <span dir="ltr"><<a href="mailto:jeff@publiclab.org" target="_blank">jeff@publiclab.org</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">So one thing I like about the contrib.json file is that it'd have a BOM requirement with potentially optional things like prices, links for where to buy materials, etc.<div><br></div><div><p style="margin:0px 0px 10px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:20px">I had some ideas (talking with <a href="http://publiclab.org/profile/rjstatic" style="color:rgb(0,136,204);text-decoration:none" target="_blank">RJ Steinert</a> of Farm Hack) about how a more Bower- or NPM-style utility could parse such files... these are just roughly sketched out ideas -- say we called it "newt":</p><ul style="padding:0px;margin:0px 0px 10px 25px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:14px;line-height:20px"><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt init</code> -- would run a text-based questionnaire to generate contrib.json file</li><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt compile bom</code> -- aggregate/merge BOMs of nested projects</li><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt compile bom <string></code> -- aggregate/merge BOMs with links matching provided <code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">string</code> like "<a href="http://digikey.com" target="_blank">digikey.com</a>"</li><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt compile price <int></code> -- calculate unit price for <code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">int</code> units</li><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt compile contributors</code> -- compile contributors of nested projects</li><li><code style="padding:2px 4px;font-family:Monaco,Menlo,Consolas,'Courier New',monospace;font-size:12px;color:rgb(221,17,68);border-radius:3px;white-space:nowrap;border:1px solid rgb(225,225,232);background-color:rgb(247,247,249)">newt register</code> -- makes searchable, tests for presence of req'd docs, clones repos or zips</li></ul><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><span style="line-height:20px">Updated my post in the comments here, where there's also been some discussion about versioning: <a href="http://publiclab.org/notes/warren/02-24-2015/standardizing-open-source-hardware-publication-practices-with-contributors-json#c11215" target="_blank">http://publiclab.org/notes/warren/02-24-2015/standardizing-open-source-hardware-publication-practices-with-contributors-json#c11215</a></span></font></div></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div><div><font color="#333333" face="Helvetica Neue, Helvetica, Arial, sans-serif"><br></font></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 24, 2015 at 7:35 PM, Roy Nielsen <span dir="ltr"><<a href="mailto:amrset@gmail.com" target="_blank">amrset@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"><div><div>Hello,<br><br>One possibility would be to require a "BOM" or bill of materials that is required for an OSHWA certified design. Perhaps something like the following for an embedded board:<br><br></div><div>* contributors.jason<br></div>* Project BOM - in the part descriptions - includes whether a part is open source or closed source <br> (ie processors, complex chips, etc)<br></div><div>* Schematics list - including descriptions & if the schematics are modifiable (ie, not pdf)<br></div><div>* License<br></div><div>* Hardware Design Documentation<br></div><div>* Software Design Documentation & License (if applicable, like firmware)<br></div><div>* Connectors - if they are open design/interface<br><br></div><div>anything else?<br><br>Score could possibly be based on what of the above is available . .<br><br></div><div>Regards,<br></div><div>-Roy<br><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 24, 2015 at 4:15 PM, Pablo Kulbaba <span dir="ltr"><<a href="mailto:pablokulbaba@gmail.com" target="_blank">pablokulbaba@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 bgcolor="#FFFFFF" text="#000000">
On the validation via a community or a specific group of people,
maybe the initial open community can provide a seedstock to raise
educated people to form a later trusted group of people that gives
an ulterior certification.<br>
<br>
PD: Had to search JSON. <br><div><div>
<br>
<div>On 24/02/2015 08:00 p.m., Mario Gómez
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>@jeff:<br>
<br>
That's great! It can even work both ways: If you already
have a JSON you can provide the URL to automatically
calculate the indicator for your project and vice versa: if
you complete the questionnaire it could automatically
generate the JSON file that you can include in your project
as you propose that would be easy to do.<br>
<br>
</div>
<div>Sadly I'm a little busy this week but let me see if I can
program a functional prototype so we can experiment how it
could work for the next month. (<span lang="en"><span>I would not mind</span>
<span>if someone</span> else <span>wants
to help)</span></span></div>
<div><br>
@Javier:<br>
<br>
</div>
<div>I personally like the idea of the community, because if
the process is straight forward, verifiable and transparent
what matters is the result of the evaluation system and not
the person/group of persons doing the evaluation. This is
assuming that the evaluation system provides means to
minimize/prevent abuses (That's why I consider important to
also implementing a meta-evaluation system).<br>
<br>
However... being certified from a trusted group of people
it's really important and I think that the OSHWA could be an
appropriate group to do that. But let's hear more opinions,
I think that it's possible to build something simple that
helps people to follow the OSHW philosophy in their
projects.<br>
</div>
<div><br>
Regards,<br>
Mario.<br>
<div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 24, 2015 at 3:54 PM,
Jeffrey Warren <span dir="ltr"><<a href="mailto:jeff@publiclab.org" target="_blank">jeff@publiclab.org</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">I really like this idea!
<div><br>
</div>
<div>Somewhat related is this idea from chatting with
Alicia Gibb a few months ago, of a contributors.json
file which would fulfill (with links, short
descriptions, etc) all the terms of the OSH definition. </div>
<div><br>
</div>
<div>I finally typed up the idea and our sample format
here:</div>
<div><br>
</div>
<div><a href="http://publiclab.org/notes/warren/02-24-2015/standardizing-open-source-hardware-publication-practices-with-contributors-json" target="_blank">http://publiclab.org/notes/warren/02-24-2015/standardizing-open-source-hardware-publication-practices-with-contributors-json</a><br>
</div>
<div><br>
</div>
<div>Love to hear input. Perhaps the questionnaire could
generate such a file. At Public Lab, it'd be interesting
for the file to be auto-generated from our tool wiki
pages. The nice part about it is that it's not
specifying a way of browsing or aggregating projects (as
other folks are exploring that space) but specifies a
standard way to make the relevant/required information
available for such projects to scrape/consume. Also,
it's easy enough to write by hand and include in a
github repository. </div>
<div><br>
</div>
<div>Best,</div>
<div>Jeff</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 24, 2015 at 3:55
PM, Javier Serrano <span dir="ltr"><<a href="mailto:Javier.Serrano@cern.ch" target="_blank">Javier.Serrano@cern.ch</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Mario,
I think this is a great idea. I see this can play
a role in the<br>
solution to one of the biggest problems of OSHW:
how to make sure<br>
developers have more incentives to publish their
work. Economic<br>
incentives in particular. An OSHW label could give
(more) prestige to<br>
developers who hold it and induce purchaser-driven
growth of OSHW. We<br>
are already seeing that prestige is a big element
in the success of OSHW<br>
companies. A well advertised and supported label
or mark could enlarge<br>
the population of savvy customers.<br>
<span><br>
On 02/24/2015 05:58 PM, Mario Gómez wrote:<br>
> The idea is that the community validates if
you are telling the truth.<br>
> To prevent abuse a meta-validation system
could be implemented were you<br>
> can "evaluate the evaluators" to see if
their are being fair on their<br>
> evaluations.<br>
<br>
</span>One alternative is to entrust the OSHWA
with that role. "Community" is a<br>
vague term. If I have to trust someone on whether
a piece of software is<br>
free software I will trust the FSF over the
"community" any day. One way<br>
of doing it would be through a creative use of
marks or labels, in the<br>
vein of what OHANDA [1] proposes. See also the
work of the Wikimedia<br>
Foundation [2] in this regard. In this scenario,
developers have a<br>
natural incentive to not misuse the mark, because
they can be sued with<br>
all the arsenal of trademark law if they do.<br>
<br>
Cheers,<br>
<br>
Javier<br>
<br>
[1] <a href="http://www.ohanda.org/" target="_blank">http://www.ohanda.org/</a><br>
[2] <a href="http://wikimediafoundation.org/wiki/Trademark_policy" target="_blank">http://wikimediafoundation.org/wiki/Trademark_policy</a><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>
</div>
</div>
</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>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
discuss mailing list
<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a>
<a href="http://lists.oshwa.org/listinfo/discuss" target="_blank">http://lists.oshwa.org/listinfo/discuss</a>
</pre>
</blockquote>
<br>
</div></div><span><font color="#888888"><pre cols="72">--
PabloK</pre>
</font></span></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">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>