At the end of this past year we started to consider the possibility of making our motherboard Open Source Hardware (OSH). After discussing the idea with the hardware producer, both sides agreed that this was a good idea. We announced this new challenge at the beginning of the year and now we think is the perfect time to clarify the implications of making the motherboard Open Source Hardware. To explain it better, we are going to formulate and respond to a couple of questions.
What is open source hardware?
It seems difficult to explain what is OSH. A complete and detailed explanation can be found on the OSHWA definition page, but simplifying it even further, we can say that OSH is hardware made in such a way that its design is publicly available. Not only that, the documentation provided to understand and reproduce the device should be friendly, in terms of allowing its edition and improvements. So a PDF file containing the schematics is not enough to describe a hardware device as open source hardware. To open source a hardware project, the complete set of CAD and description files should be provided, enabling for instance the edition of the circuits. Of course if any firmware is used to make the hardware work it should be also available as open source code.
The problem for a project like ours is attempting to reach a complete degree of openness. A notebook uses many components which are created by third party companies and, as can be imagined, nearly all of them are under proprietary licenses. In many cases, if you want to use them you have to sign an NDA agreement with their maker (for instance, NXP for a PPC processor). Furthermore, the signature of an NDA means that you can not reveal particular pieces of information in relation to that item.
The OSHWA also refers to this particular problem when explaining the process of awarding a certificate to hardware for achieving the satus of being Open Source Hardware:
“However, that does not necessarily mean that the entire project must or will be open source. If the creators used third party closed components outside of their control, they are unable – and are therefore not required – to open source those components. While it is strongly prefered to use open components when possible, OSHWA recognizes the reality that this is not always possible”
So, what’s our plan?
We want to be as open as possible. We will publish all the CAD files, specifications and any other documentation in a way that could be usable. Of course we will share our source code too (firmware and drivers). On the other hand, we will not be able to make public any third party resources covered by an NDA.
One more thing we will do is give preference to any component that could be considered open source if it accomplishes what we need. However, we need to be practical too, so the selection could be a different component if the open source hardware component lacks desired features.
Finally, where are we in in this process?
As we announced a couple of weeks ago, we have constituted the Power Progress Community association this past summer and the members of the project are currently in the process of joining the assocation by completing our membership application and paying the yearly membership fee (30 Euro). WIth that, Roberto is currently presiding over the association and soon we will have the first NDA agreements signed.
Power Progress Community logo
Another important point to quickly cover is the list of hardware components for the PPC notebook. The selection of these components is not quite completed yet, but we now feel this aspect of the project is most important so it is currently our main focus. Once the list of hardware components is finalized we will release this information in another project update. Look for that in the very near future.
