It makes sense to make people in INPUT_OWNERS owners of the file itself.

Bug: none
Test: none
Change-Id: Ia3fdfd4bb7a009abf8e9e17e37756987cd343ea8

Change-Id: I87e21b50a247f82d65a3cd46cd1612676d9dcbe0

Assign ownership to the AnrTimer files in the java source, java unit
test, and jni directories.

Bug: 282428924

Test: none - OWNERS only

Change-Id: I208296bc0cf8369d59ef51c620f50939f843173d

Test: tree hugger
Bug: 292141694
Merged-in: If4d650dc175a5a78cf8844dfed2217c19f2d5790
Change-Id: I19ed7505bfd0c71d811f98409542688094944aeb

- Add "framework-minus-apex.ravenwood".
- Update the behavior of: --default-throw:
  - Now this will "keep" the subject classes and fields.
- When a 'throw' directive is specified on a static initializer,
  it's now handled as 'keep', because otherwise the class
  wouldn't be usable.

Test: ./scripts/run-all-tests.sh
Test: m framework-minus-apex.ravenwood
Bug: 292141694
Change-Id: If4d650dc175a5a78cf8844dfed2217c19f2d5790

Test: none
Change-Id: I122b44261ac892ebab2c0867c27b9b9badc2f0bc

We took the whole build system team out, but now the list doesn't have backups.

And take out xoogler.

Test: none
Change-Id: Ib9e10474e95f8f2334f226076c206dbd83a8c2ba

The platform build team isn't equipped with the deep frameworks context to review changes. The Android.bp and Android.mk changes should be reviewed by folks who work on frameworks day-to-day.

In any case, there are members on the platform build team with Global Approver powers, in case we need overriding in the future.

Change-Id: I05324a25d0c6037b6240f209bd4b23a740d440fd
Test: N/A

Bug: 281584180

Make Shai Barack (shaibay) and Lee Shombert (shombert) owners of the
android.database.sqlite package.  Add these owners as owners of the
associated test directory and the jni files.

Test: N/A

Change-Id: I848cfe99fdc26b383b8afdae4e3ef3ad67e967d3

Soong team has cleaned up their OWNERS file, so add back hansson
to the frameworks/base build file owners.

We'll explore migrating all the API related build rules into the
api subdir, which would allow removal from the global file.

Change-Id: Ie9f6a22376b49abec5e45c3b805e00d87361101d

calin@ no longer works on Android.

Test: TH
Change-Id: I21499fda78b9cf644d4ecbee4ca1b28a6bdc3dc6

We've had a hard time finding owners for certain HAL changes and fuzzing
changes. I would like to have OWNERS here to help fill in the gaps.

Bug: N/A
Test: N/A
Change-Id: Ic734d4bd925d77ea06b4db4fd225105f33e48ad0

Soong team is now owner too.

Test: N/A

Change-Id: I9af77c6f3e9e63032da278abe3b020bba16c51ab

Soong having OWNERS in frameworks/base is useful to enable LSCs;
however, they shouldn't appear in review suggestions except as a
fallback.

Test: n/a
Change-Id: I86618b66e51893908478def9fc455a3dfde146f0

Since TEST_MAPPING files can reference test suites flung far across
the source tree, allow anyone to make changes to them.

Bug: 174932174
Test: none
Change-Id: I11dd436ac55e516263a587f9f82b17ce56e9e2e2

This target is used for TradeFed dependencies and can be managed
separately by these two teams.

Bug: 181921006
Test: Manual
Change-Id: Ibcfeef30c8cb88e244561cac99c034981b84ed80

These top-level owners are only designed to offer fallback support
in situations such as local OWNERS files becoming stale, large-scale
changes, etc.

When local owners have been defined by a sub-team, only those owners
should appear in the Gerrit suggestions list.

Bug: 181661570
Test: none
Change-Id: Ib201cb32e97707d35df077128f4c5e8205124b7f

The proto build rules are quite large and makes the top-level Android.bp
file difficult to navigate. Move them to a separate file.

Bug: 185128417
Test: m
Change-Id: I5719ba0fa8e03dcfca0cc32dc30db3f87ea4e3cd

The proto build rules are quite large and makes the top-level Android.bp
file difficult to navigate. Move them to a separate file.

Bug: 185128417
Test: m
Merged-In: I5719ba0fa8e03dcfca0cc32dc30db3f87ea4e3cd
Change-Id: I5719ba0fa8e03dcfca0cc32dc30db3f87ea4e3cd

Bug: 174932174
Test: none
Change-Id: I32290974d815e42a4626b40de865d720b01dcc44

API current.txt files are already covered by the API-Review label through
https://android.git.corp.google.com/All-Projects/+/refs/meta/config/rules.pl#226.

Test: n/a
Change-Id: Ib0f8272cc4dfe58b41804ef8c0951b7026cd0a59

Change-Id: I4785795e4bb9f232ae41674bb56322f5c97871bb

Iteration based on areas of tree where detailed ownership was found
to be missing during routine code reviews.

Also add more detailed examples to OWNERS.md.

Bug: 174932174
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Change-Id: I46ccef33b34594181ae8dc62973d68020f827d6b

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

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 begins defining top-level OWNERS lists,
including a general catch-all for string translations.

Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Change-Id: Ie7ac3302d40a717fa048115cca2ea4359de64959