First step: More info about what 'model' means in the Goldeneye world. If we are going to make this change it should be soon.

Assigning to Christine.

Is there a naming glossary in the goldeneye world? Also, what is a 'sub-board' a sub of? It sounds like there's a hierarchy intent. 

No, no glossary per se, but a "Board" in the GE world is essentially the software image for a "Device" which represents the hardware.  We've had requests to add additional device metadata to track model numbers, and I think this corresponds more to SKUs.  If we end up also having "Model" as a related (one to many) entity of a Board, I think it could be pretty confusing.

Perhaps we should separate the concept of model (something supported by a board) and sku (a think with particular devices)?

So:

Board ‒ board overlay, corresponding to a build. For each board we need a builder. A board may support multiple models.

Model ‒ a single model in the market. It may or may not share design elements with other models, but we want to distinguish it from other models due to the physical design, OEM or ODM. This has its own hardware ID.

SKU - a particular stock-keeping unit within a model, differentiated by different physical design or components. Shares a hardware ID with other SKUs in the same model.

The advantage of using 'SKU' is that it is a widely understood term.

My original glossary in the design doc here:

https://docs.google.com/document/d/1XG8motvGyn-yevrzkskhUuhynWi3o86VjrlGs9p94fw/edit#bookmark=id.kc0rvdq2qik8

No change on this so I'm going to drop this idea. Please let me know if you still think it has legs.