I have been accumulating a collection of posts about open source hardware and software. It is past time for me to share them.
- A discussion on the importance of documentation, especially the right kind of documentation – The discussion on death marches (waiting until the last minute and then trying to document all the things) is something we have experienced at Mach 30, and is specifically why our work on OSHW ground rules includes three separate behaviors around when you document projects (before, during, and after you take any actions)
- OSHWA’s new OSHW Certification Process has gotten some interesting reactions online lately, and much of it expressing concerns about certification
- Saar Drimer writes about long standing concerns over branding in OSHW and believing the certification process is misguided – having both argued strongly in favor of the OSHW logo and having seen many projects that were Open Source in Name Only, I think we need to do more than just public shaming, and the certification process proposed by OSHWA is among the least invasive options that I heard discussed.
- Here is another response the OSHW Certification Process, this time from Evil Mad Scientist Laboratories – this post is more nuanced, and I appreciate the well thought out listing of pros and cons and some thoughts on how OSHWA can be successful with the certification process
- And here is OSHWA’s response to community reactions to the certification process – I think this is a good first attempt to clarify where OSHWA is headed, and I like that it references the Evil Mad Scientist post; OSHWA needs to keep up their communications efforts on this project (telling us what is working and what is not) to allay the concerns of the community and to make the evolving process clear to everyone (good and bad actors alike)