Every Build is a Fork: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Hear more about this concept, as it has profound implications on how open hardware is documented: | Hear more about this concept, as it has profound implications on how open hardware is documented: | ||
The summary is, in jargon - there is no uniform compiler in hardware. Thus, every build is unique. Therefore every build must be treated as a fork - ie - documented in its entirety under a different project. | |||
In popular language - Every build is unique (we can explain various reasons why this holds true). Because every build is unique, it must be documented in its entirety as a separate project - so that there is no confusion as far as what documentation is relevant to a specific project. | |||
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/coOF23mOjSc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> | <html><iframe width="560" height="315" src="https://www.youtube.com/embed/coOF23mOjSc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> | ||
Revision as of 20:23, 3 August 2022
Hear more about this concept, as it has profound implications on how open hardware is documented:
The summary is, in jargon - there is no uniform compiler in hardware. Thus, every build is unique. Therefore every build must be treated as a fork - ie - documented in its entirety under a different project.
In popular language - Every build is unique (we can explain various reasons why this holds true). Because every build is unique, it must be documented in its entirety as a separate project - so that there is no confusion as far as what documentation is relevant to a specific project.