[Discuss] Proposal: Open Source Hardware Score/Index
jeff at publiclab.org
Tue Feb 24 21:54:54 UTC 2015
I really like this idea!
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.
I finally typed up the idea and our sample format here:
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.
On Tue, Feb 24, 2015 at 3:55 PM, Javier Serrano <Javier.Serrano at cern.ch>
> Mario, I think this is a great idea. I see this can play a role in the
> solution to one of the biggest problems of OSHW: how to make sure
> developers have more incentives to publish their work. Economic
> incentives in particular. An OSHW label could give (more) prestige to
> developers who hold it and induce purchaser-driven growth of OSHW. We
> are already seeing that prestige is a big element in the success of OSHW
> companies. A well advertised and supported label or mark could enlarge
> the population of savvy customers.
> On 02/24/2015 05:58 PM, Mario Gómez wrote:
> > The idea is that the community validates if you are telling the truth.
> > To prevent abuse a meta-validation system could be implemented were you
> > can "evaluate the evaluators" to see if their are being fair on their
> > evaluations.
> One alternative is to entrust the OSHWA with that role. "Community" is a
> vague term. If I have to trust someone on whether a piece of software is
> free software I will trust the FSF over the "community" any day. One way
> of doing it would be through a creative use of marks or labels, in the
> vein of what OHANDA  proposes. See also the work of the Wikimedia
> Foundation  in this regard. In this scenario, developers have a
> natural incentive to not misuse the mark, because they can be sued with
> all the arsenal of trademark law if they do.
>  http://www.ohanda.org/
>  http://wikimediafoundation.org/wiki/Trademark_policy
> discuss mailing list
> discuss at lists.oshwa.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss