<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body 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>
<br>
<div class="moz-cite-prefix">On 24/02/2015 08:00 p.m., Mario Gómez
wrote:<br>
</div>
<blockquote
cite="mid:CAJ9n+w0d43vys7rLh1JN+dtkYpMCTsqz_it3RgDtdemi9LkxwA@mail.gmail.com"
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 id="result_box"
class="" lang="en"><span class="">I would not mind</span>
<span class="">if someone</span> else <span class="">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 moz-do-not-send="true"
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 moz-do-not-send="true"
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 class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 24, 2015 at 3:55
PM, Javier Serrano <span dir="ltr"><<a
moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://www.ohanda.org/" target="_blank">http://www.ohanda.org/</a><br>
[2] <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:discuss@lists.oshwa.org"
target="_blank">discuss@lists.oshwa.org</a><br>
<a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a><br>
<a moz-do-not-send="true"
href="http://lists.oshwa.org/listinfo/discuss"
target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a>
<a class="moz-txt-link-freetext" href="http://lists.oshwa.org/listinfo/discuss">http://lists.oshwa.org/listinfo/discuss</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
PabloK</pre>
</body>
</html>