Skeleton of clarifying shared service ownership

Why is this change being made?

Recently, there have been independent threads discussing ownership model of shared services and components in the GitLab technology stack, for example PostgreSQL database and Workhorse.

Although the current decentralized ownership model worked reasonably well in the past, GitLab engineering has evolved a lot and it appears necessary to add more clarity to the shared services and components ownership so that nothing falls into crack and engineering keeps running highly efficient.

The goal of this MR is trying to establish a skeleton for ownership review and decision making. The outcome is an acceptable set of ownership models and an exhaustive list of shared services and components in the product stack.

The next step (not part of this MR) is to spin up dedicated MRs to land on consensus for each service and component.

How to work with this MR

1. Ownership models
   1. Review description of enlisted models, suggest changes to get them in shape.
   2. Propose other creative models with sufficient details how they work in practice.
2. List of shared services and components
   1. Review current list and suggest corrections and changes.
   2. Add missing services and components.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.