Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b84eaab3 authored by Jeff Sharkey's avatar Jeff Sharkey Committed by Automerger Merge Worker
Browse files

Improve OWNERS coverage across frameworks/base/. am: 061c2ec3 

Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1519382

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: I1218107820d89a570b55768ed6f9b223cd0db5fc
parents 5d775cd0 061c2ec3

OWNERS

0 → 100644
+19 −0
Original line number Diff line number Diff line 
# This top-level list should remain narrowly defined as team leads; individual

# teams are strongly encouraged to define narrower OWNERS files at deeper

# levels within the source tree; see OWNERS.md for more details

dsandler@android.com

dsandler@google.com

hackbod@android.com

hackbod@google.com

jsharkey@android.com

jsharkey@google.com

michaelwr@google.com

nandana@google.com

narayan@google.com

ogunwale@google.com

svetoslavganov@android.com

svetoslavganov@google.com

yamasani@google.com



# Support bulk translation updates

per-file */res*/values*/*.xml = byi@google.com

OWNERS.md

0 → 100644
+34 −0
Original line number Diff line number Diff line 
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.



The structure of `frameworks/base/` is unique among Android repositories, and

it's evolved into a complex interleaved structure over the years.  Because of

this structure, the best place to authoritatively define `OWNERS` can vary

wildly, but here are some common patterns:



* `core/java/` contains source that is included in the base classpath, and as

such it's where most APIs are defined:

  * `core/java/android/app/`

  * `core/java/android/content/`

* `services/core/` contains most system services, and these directories

typically have more granularity than `core/java/`, since they can be refactored

without API changes:

  * `services/core/java/com/android/server/net/`

  * `services/core/java/com/android/server/wm/`

* `services/` contains several system services that have been isolated from the

main `services/core/` project:

  * `services/appwidget/`

  * `services/midi/`

* `apex/` contains Mainline modules:

  * `apex/jobscheduler/`

  * `apex/permission/`

* Finally, some teams may have dedicated top-level directories:

  * `media/`

  * `wifi/`



Area maintainers are strongly encouraged to list people in a single

authoritative `OWNERS` file in **exactly one** location.  Then, other paths

should reference that single authoritative `OWNERS` file using an include

directive.  This approach ensures that updates are applied consistently across

the tree, reducing maintenance burden.

ZYGOTE_OWNERS

0 → 100644
+5 −0
Original line number Diff line number Diff line 
calin@google.com

chriswailes@google.com

maco@google.com

narayan@google.com

ngeoffray@google.com

core/api/OWNERS

0 → 100644
+2 −0
Original line number Diff line number Diff line 
# API changes are managed via Prolog rules, not OWNERS

*

core/res/OWNERS

0 → 100644
+17 −0
Original line number Diff line number Diff line 
adamp@google.com

alanv@google.com

dsandler@android.com

dsandler@google.com

hackbod@android.com

hackbod@google.com

jsharkey@android.com

jsharkey@google.com

michaelwr@google.com

nandana@google.com

narayan@google.com

ogunwale@google.com

patb@google.com

svetoslavganov@android.com

svetoslavganov@google.com

toddke@google.com

yamasani@google.com