4 Commits

Author SHA1 Message Date
Nataniel Borges
b81392c9cd Add pablogamito to flicker test owners
Test: check owners file
Change-Id: If8adecda0d23d6d673825695e57813b281c0f6bc
2021-11-09 19:11:37 +01:00
Nataniel Borges
b8d53f9ceb Include component ID in OWNERS file
By default all flicker tests use the Winscope component.

Change-Id: Ibacb1d247807ac1cbef6b4219b8966a87eccdb5c
Test: check the owner files
2021-02-09 20:36:42 +00:00
Vadim Caen
9e9ff33963 Adding Natanieljr@ to flicker owners
Change-Id: If0339feee4aca5ee30efa582e9751f9023c00eee
2020-12-09 11:02:20 +00:00
Jeff Sharkey
52b9862f87 Improve OWNERS coverage across frameworks/base/.
As general background, OWNERS files expedite code reviews by helping
code authors quickly find relevant reviewers, and they also ensure
that stakeholders are involved in code changes in their areas.

Some teams under frameworks/base/ have been using OWNERS files
successfully for many years, and we're ready to expand them to cover
more areas.  Here's the historical coverage statistics for the last
two years of changes before these new OWNERS changes land:

-- 56% of changes are fully covered by OWNERS
-- 17% of changes are partially covered by OWNERS
-- 25% of changes have no OWNERS coverage

Working closely with team leads, we've now identified clear OWNERS on
a per-package basis, and we're using "include" directives whenever
possible to to simplify future maintenance.  With this extensive
effort, we've now improved our coverage as follows:

-- 98% of changes are fully covered by OWNERS
-- 1% of changes are partially covered by OWNERS
-- 1% of changes have no OWNERS coverage

This specific change is automatically generated by a script that
identifies relevant "include" directives.

Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Merged-In: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Change-Id: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
2020-12-08 08:36:28 -07:00