Contact Details
No response
Problem Description
To prepare the BB catalog for long-term maintenance and relavance, it is suggested to simplify the BB temlpate structure: reduce the template to a small required core: Name, Tag(s), Layer, one-line Description, Rationale, Known Implementation/link, Source availability & license, State/maturity.
Everything else (ID, Priority, Compose BB(s), Potential obstacles, detailed Design/Build prerequisites, Vehicle API Relevant, Governance, Dependencies to other Clusters) could move to an optional "Details" section, or be dropped entirely — these are at 2–50% fill rate today, so do not add anything and make the relevant content harder to parse.
Contact Details
No response
Problem Description
To prepare the BB catalog for long-term maintenance and relavance, it is suggested to simplify the BB temlpate structure: reduce the template to a small required core: Name, Tag(s), Layer, one-line Description, Rationale, Known Implementation/link, Source availability & license, State/maturity.
Everything else (ID, Priority, Compose BB(s), Potential obstacles, detailed Design/Build prerequisites, Vehicle API Relevant, Governance, Dependencies to other Clusters) could move to an optional "Details" section, or be dropped entirely — these are at 2–50% fill rate today, so do not add anything and make the relevant content harder to parse.