Should we officially "adopt" one of the existing component codebases (WVUI, WiKit, etc.) or start a new repository? What kind of policies around governance should we adopt? Versioning, contribution policy, etc. We have already had many of these conversations in relation to WVUI; some/most of that work may apply here too.
**Considerations**
* **Contribution policy:**
** WiKit and WVUI have some existing documentation about how to contribute:
*** WiKit: [[ https://wmde.github.io/wikit/?path=/story/documentation-contributing--page | Contributing ]], [[ https://wmde.github.io/wikit/?path=/story/documentation-how-to-modify-existing-components--page | modifying existing components ]], [[ https://wmde.github.io/wikit/?path=/story/documentation-how-to-create-reusable-components-overview--page | creating reusable components ]]
*** WVUI: [[ https://github.com/wikimedia/wvui/blob/master/CONTRIBUTING.md | contributing ]]
** We should also consider how to facilitate contributes from those outside the Design Systems team: what base work should be prioritized to enable more effective contributions, like getting the design token architecture implemented? What will the process be for teams that need a component that doesn't exist yet in the shared library?
**Relevant links**
* T272885: list of Vue projects and components in the wiki-verse (may be somewhat outdated; please update it as needed)
**Decisions**
1. Which codebase, existing or new, will we use as the canonical, shared component library?
2. How will the Design Systems team roll out releases and version those releases?
3. What is the contribution policy for changes and new components?
4. What are the library's design principles, and where will they be documented?