20.6 Repository Ownership [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

===== 20.6 Repository Ownership =====

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:20-risks-and-open-decisions:start | Return to Risks and Open Decisions ]]

The team must decide who owns the Phase 0 repository, who can approve changes, and how the repository connects to the broader Financial Systems Archetype work.

Open repository ownership decisions may include:

  - Which repository platform the team uses.
  - Which organization or project account owns the repository.
  - Who has administrative access.
  - Who can merge into protected branches.
  - Who can approve baseline changes.
  - Who maintains the handbook and repository documentation.
  - Who maintains scripts, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] workflows, containers, and CI configuration.
  - How the team handles external contributors or reviewers.

Repository ownership affects access control, review discipline, baseline tagging, release preparation, and long-term maintainability. The team should record repository ownership decisions in an implementation decision record or project governance note.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>