blob: e737c7f874f22bf2daeb6053ac586c38bb3e98d4 [file] [log] [blame]
Andrew Jefferyd6df5fa2022-10-10 21:44:09 +10301# OWNERS
2# ------
3#
4# The OWNERS file maintains the list of individuals responsible for various
5# parts of this repository, including code review and approval. We use the
6# Gerrit 'owners' plugin, which consumes this file, along with some extra
7# keywords for our own purposes and tooling.
8#
9# For details on the configuration used by 'owners' see:
10# https://gerrit.googlesource.com/plugins/owners/+/refs/heads/master/owners/src/main/resources/Documentation/config.md
11#
12# An OWNERS file must be in the root of a repository but may also be present
13# in any subdirectory. The contents of the subdirectory OWNERS file are
14# combined with parent directories unless 'inherit: false' is set.
15#
16# The owners file is YAML and has [up to] 4 top-level keywords.
17# * owners: A list of individuals who have approval authority on the
18# repository.
19#
20# * reviewers: A list of individuals who have requested review notification
21# on the repository.
22#
23# * matchers: A list of specific file/path matchers for granular 'owners' and
24# 'reviewers'. See 'owners' plugin documentation.
25#
26# * openbmc: A list of openbmc-specific meta-data about owners and reviewers.
27# - name: preferred name of the individual.
28# - email: preferred email address of the individual.
29# - discord: Discord nickname of the individual.
30#
31# It is expected that these 4 sections will be listed in the order above and
32# data within them will be kept sorted.
33
34owners:
35- andrew@aj.id.au
36- patrick@stwcx.xyz
37
38reviewers:
39- bradleyb@fuzziesquirrel.com
40- edtanous@google.com
41- jason.m.bills@linux.intel.com