[Discuss] A guide to open source hardware

[Tiberius Brastaviceanu]

See www.SENSORICA.co for open innovation and peer production models.
Within SENSORICA we have the habit of publishing not only the final design
files but and the working documents wlthat leat to that design, exposing
past mistakes and their solutions, possible pitfalls, decision making
processes, etc.
>From my 6 years experience developing open hardware in an Open Value
Network environment I can say that it happens very often that someone tries
to make an improvement to something and goes where others have failed in
the past. Documenting the path to the final design has huge value.
On Aug 17, 2016 12:07 PM, "Jay Patel" <rockworldmi at gmail.com> wrote:

> is OpenBSD more compatible with OSHWA project?
>
>
> On Tue, Aug 16, 2016 at 9:46 PM, Matt Maier <blueback09 at gmail.com> wrote:
>
>> In terms of a structured way to capture all of the documentation you
>> describe, this is a process I demonstrated a while back for Open Source
>> Ecology's LifeTrac tractor http://opensourceecology.org/wiki/Distributed_
>> Collaboration
>>
>> I'm working on a better way http://github.howstr.com/
>>
>> Your write up is pretty good. You should add a section about keeping the
>> documentation up to date as the project evolves. It also kind of highlights
>> the reason open source hardware documentation is so scant...it's a lot of
>> work and it's not clear to many what they get back for doing all that work.
>>
>> We need to make it easier, so that it's not so much work.
>>
>>
>>
>> On Fri, Jul 22, 2016 at 10:31 AM, Bonvoisin, Jeremy <
>> jeremy.bonvoisin at tu-berlin.de> wrote:
>>
>>> Hi,
>>>
>>>
>>>
>>> I’m a researcher at the Technical University Berlin where we have a
>>> newly started French-German research project on open source hardware
>>> <http://130.149.46.183/wiki/index.php/OPEN!_Methods_and_tools_for_community-based_product_development>.
>>>
>>>
>>>
>>>
>>> I would like to share with you a document we made to summarize the best
>>> practices we observed through the analysis of a large number of open source
>>> hardware projects. The page is named “a guide to open source hardware
>>> <http://130.149.46.183/wiki/index.php/A_guide_to_Open_Source_Hardware>”
>>> and attempts giving practical guidance regarding documentation of open
>>> source hardware products, especially for mechanic products. This is some
>>> sort of extension of the “Best Practices of Open Source Hardware 1.0
>>> <http://www.oshwa.org/sharing-best-practices/>” of the OSHWA.
>>>
>>>
>>>
>>> I would be glad to get your impressions, feedback, critics or even
>>> propositions for further development of this document.
>>>
>>>
>>>
>>> I am also open for merging this document with existing initiatives, for
>>> example if there are discussions about a second version of the “best
>>> practices” of the OSHWA.
>>>
>>>
>>>
>>> Thanks in advance for your reactions!
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Jérémy Bonvoisin
>>>
>>>
>>>
>>> Dr. Jérémy Bonvoisin
>>>
>>> Ingénieur esiea – Research engineer
>>>
>>> Institut für Werkzeugmaschinen und Fabrikbetrieb - IWF
>>>
>>> Fachgebiet Industrielle Informationstechnik
>>>
>>> Technische Universität Berlin
>>>
>>> Mail: jeremy.bonvoisin at tu-berlin.de
>>>
>>> Tel.: +49 (0)30 39006 358
>>>
>>> Raum: PTZ 563
>>>
>>>
>>>
>>> _______________________________________________
>>> discuss mailing list
>>> discuss at lists.oshwa.org
>>> http://lists.oshwa.org/listinfo/discuss
>>>
>>>
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at lists.oshwa.org
>> http://lists.oshwa.org/listinfo/discuss
>>
>>
>
> _______________________________________________
> discuss mailing list
> discuss at lists.oshwa.org
> http://lists.oshwa.org/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oshwa.org/pipermail/discuss/attachments/20160817/897256ab/attachment.html>