The design system's governance model outlines the steps and collaborative processes involved in the reusage, creation, modification and deprecation of system components (either core or project one-offs). It tries to establish roles and responsibilities, and set clear collaboration guidelines that will enable teams to actively contribute to the system.
==== Objectives
- **Validate the high-level paths and processes involved in the creation of components, from the appearance of the component need until its release.**
{F34568005}
- **Align on the initial model's guiding principles:**
- **Transparency**: Tasks status and progress is clearly shared and made accessible to all stakeholders. Gatekeeping, development, design and product decisions are made in the open.
- **Enablement rather than enforcement**: System consumers are considered contributors, and should be empowered by the core team to make decisions and own parts of the system. Product teams have a level of choice and impact on the system (e.g. suggesting components or variants, suggesting fixes or enhancements, or providing feedback for the governance model itself).
- **Knowledge sharing rather than knowledge silo**: Contributors should have support and access to resources that allows them to understand and influence the system's workflows, methodologies, standards and infrastructure.
==== Outcome
Agree on the values that motivate the model.
Preliminary DACI/Governance model flow diagram:
https://www.figma.com/file/cnbxl3nG6CKpjaTSjXTwQk/Wikimedia-Design-System-(DS)-%E2%80%93-Governance-model%2FDACI