blob: aa05b6b258945925d170cbee4edb2ea4f3840c66 [file] [log] [blame]
Andrew Jefferye2642982018-05-19 02:28:34 +09301How to use this list:
2 Find the most specific section entry (described below) that matches where
3 your change lives and add the reviewers (R) and maintainers (M) as
4 reviewers. You can use the same method to track down who knows a particular
5 code base best.
6
7 Your change/query may span multiple entries; that is okay.
8
9 If you do not find an entry that describes your request at all, someone
10 forgot to update this list; please at least file an issue or send an email
11 to a maintainer, but preferably you should just update this document.
12
13Description of section entries:
14
15 Section entries are structured according to the following scheme:
16
Bruce Mitchell673ad232021-05-10 16:57:19 -050017 X: NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>
Andrew Jefferye2642982018-05-19 02:28:34 +093018 X: ...
19 .
20 .
21 .
22
23 Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24 organization; FILE_PATH is a file path within the repository, possibly with
25 wildcards; X is a tag of one of the following types:
26
Bruce Mitchell673ad232021-05-10 16:57:19 -050027 M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
Andrew Jefferye2642982018-05-19 02:28:34 +093028 if omitted from an entry, assume one of the maintainers from the
29 MAINTAINERS entry.
Bruce Mitchell673ad232021-05-10 16:57:19 -050030 R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
Andrew Jefferye2642982018-05-19 02:28:34 +093031 these people are to be added as reviewers for a change matching the repo
32 path.
33 F: Denotes forked from an external repository; has fields URL.
34
35 Line comments are to be denoted "# SOME COMMENT" (typical shell style
36 comment); it is important to follow the correct syntax and semantics as we
37 may want to use automated tools with this file in the future.
38
39 A change cannot be added to an OpenBMC repository without a MAINTAINER's
40 approval; thus, a MAINTAINER should always be listed as a reviewer.
41
42START OF MAINTAINERS LIST
43-------------------------
44
Patrick Williams75016662020-02-04 15:47:34 -060045M: Patrick Williams <patrick@stwcx.xyz> <stwcx!>
Bruce Mitchell673ad232021-05-10 16:57:19 -050046M: William Kennington <wak@google.com> <wak!>
Vernon Mauerydb4a4a62019-05-16 08:24:41 -070047M: Vernon Mauery <vernon.mauery@linux.intel.com> <vmauery!>
Lei YU43ea4262019-12-17 10:32:10 +080048M: Lei Yu <mine260309@gmail.com> <LeiYU!>
Andrew Jefferye2642982018-05-19 02:28:34 +093049R: Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!>
50R: Adriana Kobylak <anoo@us.ibm.com> <anoo!>
Deepak Kodihallia3f2bde2020-11-26 12:08:16 +053051R: Deepak Kodihalli <deepak.kodihalli.83@gmail.com> <dkodihal!>
Bruce Mitchell673ad232021-05-10 16:57:19 -050052R: Richard Thomaiyar <richard.marian.thomaiyar@linux.intel.com> <rthomaiy!>