Facilitating hardware evolution allows cumulative improvements and branched applications that the initial developers could not anticipate. While it is likely beneficial to maintain a base version of the hardware like in a typical open-source code repository, in this work, we observed an added benefit from the branches that may evolve far from the baseline design and cannot be readily merged with it. From this viewpoint, creating simple community standards for documenting and sharing the work is more essential than investing on standards for adding features to the baseline design. In some cases, the latter approach can actually be prohibitive for the evolution process. The evolution can be further facilitated by thorough documentation, and open communication between sites on the strengths and weaknesses of the existing design.