Add codeowners file requirement for new gitlab repositories
Code ownership and reviewer selection is already handled pretty well by Danger in our main repo. When you venture outside of the main repository and towards smaller projects, figuring out code ownership and who to ask a review from becomes difficult, especially as a new recruit.
I myself struggled with code ownership quite a lot recently, examples of MRs without clear ownership
- https://gitlab.com/gitlab-org/gitlab-exporter/merge_requests/100 (has a single individual as approver, who was OOO at the time, as well as his named replacement)
- gitlab-org/gitlab-build-images!218 (merged) (unsure who owns the project, is ownership per image, etc)
- gitlab-cookbooks/gitlab-monitor!28 (closed) (haven't figured it out yet)
Using a standard CODEOWNERS file in each repository would help new recruits and most likely veterans figure out where their changes should go, and speed up the time to merge significantly outside of the main repository.
I understand backfilling code owners everywhere is going to take a while, but I figured, in handbook-first fashion, I would start by explicitly documenting it for new repositories. We can worry about the long tail of repos as we go.
Please let me know your thoughts!