Give tools/ a real OWNERS file.

tools/metrics/OWNERS

Index: tools/metrics/OWNERS
diff --git a/tools/metrics/OWNERS b/tools/metrics/OWNERS
index 10c75d5b27df9ff2034b628e58b68664604f55b5..d38b77ebaa18ccc8f341859012da32accc8e45c2 100644
--- a/tools/metrics/OWNERS
+++ b/tools/metrics/OWNERS
@@ -1,5 +1,3 @@
-set noparent

[Alexei Svitkine (slow), 2015/11/12 21:10:26]

I think removing this is dangerous on tools/metrics.

Now, if you have an LGTM from a src/OWNERS (e.g. because you needed a stamp for
chrome/ or something), you might end up submitting without a metrics reviewer
looking at your histograms.xml changes. You can do this accidentally (i.e.
because the tools told you had complete OWNERS coverage).

I don't think that's a good practice. Can we still have setnoparent at least for
the XML files? Otherwise, I feel it's too easy to accidentally land those
changes without a proper metrics review.

[Nico, 2015/11/12 21:19:15]

This is true for all OWNERS files though, right? You have to trust that people
in OWNERS files above you don't abuse their powers.
Having `noparent` is bad practice too, in general as it makes global
refactorings harder and whatnot. But if per-file noparent is possible, having it
for the xml files in this directory would be fine with me (they do seem
delicate, and per-file noparent sets a slightly worse precedent than a full
noparent). But maybe we could wait a week or two and see if this a real problem
first?

-
 asvitkine@chromium.org
 isherman@chromium.org
 jar@chromium.org