Skip to content

The Repository Folder Structure

madri edited this page Jun 23, 2025 · 5 revisions

To make it easier to manage, to find and navigate Building Block (BB) descriptions, we have directly reflected the definitions of BB-Tags, Areas in our GitHub repository’s folder structure.

root structure -  BB-Tags

To further improve orientation, we introduced additional groupings and classifications based on commonly used layered architecture models and domain-specific structures known from the automotive software world. This helps accommodate cases where multiple implementations already exist or are expected for a single Building Block description.

root structure with sub classes - here Functional Clusters

Since part of our mission is to identify gaps in the SDV ecosystem, the repository also contains BB descriptions that currently do not reference any known open implementation. To distinguish between BBs with and without implementation we have mirrored the folder structure once again in a folder called WorkInProgress:

  • Root-level folders contain BBs that reference existing implementations or external sources.
  • The WorkInProgress/ folder is a mirrored structure, where BBs are placed that describe relevant functionality — but for which no implementation or public reference is currently available.

WorkInProgress mirror - BBs without known implementation

These Building Blocks under WorkInProgress are waiting for contributions, from individuals, initiatives, projects, or organizations, that can provide an implementation reference. Once a solution is available, the BB can be reviewed and moved to the main folder structure. This dual structure makes it easier to:

  • Clearly highlight implementation gaps
  • Encourage focused collaboration and shared development

Clone this wiki locally