Last month at the Open Hardware Summit we announced the start of the OSHWA open source hardware certification program. Part of that program involved issuing unique IDs (UIDs) for each piece of registered hardware. Since we knew that low numbers would be hot properties, we decided to wait until the end of October to assign them. That allowed us to give every piece of hardware registered in the month of October a chance for the lowest possible number.
Today, thanks to the good people at random.org, we have assigned those UIDs to all pieces of hardware registered before the end of October. We have also started assigning numbers sequentially for all pieces of hardware registered since November started. You can see all of the registered hardware here.
There were 60 different projects registered from 9 different countries. Want to get your own UID? Register here!
You’re also welcome to post projects on the open source hardware community at https://www.openhardware.io. GitHub integration, 3d gerber viewer and allows authors to receive donations and more.
Cheers
Henrik
Does openhardware.io require that entries are OSHWA-compliant open source? Is there a verification process?
Well, the community keeps track of the posted projects. We only allow the following licences:
Attribution-ShareAlike (CC-BY-SA)
Attribution (CC-BY)
Balloon Open Hardware License
CERN Open Hardware License
TAPR Open Hardware License
GPL 3.0
LGPL
BSD
MIT
Apache
Public Domain
It’s ok to post a WIP projects (without source files) while the board still hasn’t been verified by the author. We wouldn’t want “newbies” to go download and order boards that still might have errors.
We also remove projects that never publishes any source files (after contacting/verifying with author).
So, yes, we verify projects manually.
The directory is looking sparse, can we finally all agree this has been a misguided effort and shut it down. Then we can get back to an educational approach to teaching about OSHW and not this self-appointed enforcer of make-believe rules?