Google's code ownership

[Seb via Digitalmars-d]

 From the recent article "Why Google Stores Billions of Lines of 
Code in a Single Repository" a very interesting excerpt about 
their code ownership [1]:

> An important aspect of Google culture that encourages code 
> quality is the expectation that all code is reviewed before 
> being committed to the repository. Most developers can view and 
> propose changes to files anywhere across the entire 
> codebase—with the exception of a small set of highly 
> confidential code that is more carefully controlled. The risk 
> associated with developers changing code they are not deeply 
> familiar with is mitigated through the code-review process and 
> the concept of code ownership. The Google codebase is laid out 
> in a tree structure. Each and every directory has a set of 
> owners who control whether a change to files in their directory 
> will be accepted. Owners are typically the developers who work 
> on the projects in the directories in question. A change often 
> receives a detailed code review from one developer, evaluating 
> the quality of the change, and a commit approval from an owner, 
> evaluating the appropriateness of the change to their area of 
> the codebase.

How about doing something similar for Phobos?
On a related note Facebook open-sourced it's "mention-bot" [2] 
that could be helpful in case no owners are defined.

[1] 
http://cacm.acm.org/magazines/2016/7/204032-why-google-stores-billions-of-lines-of-code-in-a-single-repository/fulltext
[2] https://github.com/facebook/mention-bot