Document MR feature ownership
The MR feature is one of the most active areas of GitLab in terms of contributions and overlap of product teams. Having the ownership of the MR feature clearly documented would help improve collaboration and efficiency. For example, knowing when and how the Code Review group should be involved when making decision that could affect the larger MR experience or code base.
Inspiration
- As an example of something similar: Ownership of Shared Services and Components
Scope
- Define the most appropriate ownership model (or models) when teams wish to contribute to the MR experience. For inspiration see Ownership models.
- Decide the location to document this.
- Document it.
- Add a step in the Product Development Flow's Validation track to check with owners of the areas the solution impacts if not your own. And point to the page where we end up documenting the ownership of MRs.