xref: /openbmc/pyphosphor/MAINTAINERS (revision 216b518a)
1*216b518aSAndrew JefferyHow to use this list:
2*216b518aSAndrew Jeffery    Find the most specific section entry (described below) that matches where
3*216b518aSAndrew Jeffery    your change lives and add the reviewers (R) and maintainers (M) as
4*216b518aSAndrew Jeffery    reviewers. You can use the same method to track down who knows a particular
5*216b518aSAndrew Jeffery    code base best.
6*216b518aSAndrew Jeffery
7*216b518aSAndrew Jeffery    Your change/query may span multiple entries; that is okay.
8*216b518aSAndrew Jeffery
9*216b518aSAndrew Jeffery    If you do not find an entry that describes your request at all, someone
10*216b518aSAndrew Jeffery    forgot to update this list; please at least file an issue or send an email
11*216b518aSAndrew Jeffery    to a maintainer, but preferably you should just update this document.
12*216b518aSAndrew Jeffery
13*216b518aSAndrew JefferyDescription of section entries:
14*216b518aSAndrew Jeffery
15*216b518aSAndrew Jeffery    Section entries are structured according to the following scheme:
16*216b518aSAndrew Jeffery
17*216b518aSAndrew Jeffery    X:  NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>
18*216b518aSAndrew Jeffery    X:  ...
19*216b518aSAndrew Jeffery    .
20*216b518aSAndrew Jeffery    .
21*216b518aSAndrew Jeffery    .
22*216b518aSAndrew Jeffery
23*216b518aSAndrew Jeffery    Where REPO_NAME is the name of the repository within the OpenBMC GitHub
24*216b518aSAndrew Jeffery    organization; FILE_PATH is a file path within the repository, possibly with
25*216b518aSAndrew Jeffery    wildcards; X is a tag of one of the following types:
26*216b518aSAndrew Jeffery
27*216b518aSAndrew Jeffery    M:  Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
28*216b518aSAndrew Jeffery        if omitted from an entry, assume one of the maintainers from the
29*216b518aSAndrew Jeffery        MAINTAINERS entry.
30*216b518aSAndrew Jeffery    R:  Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
31*216b518aSAndrew Jeffery        these people are to be added as reviewers for a change matching the repo
32*216b518aSAndrew Jeffery        path.
33*216b518aSAndrew Jeffery    F:  Denotes forked from an external repository; has fields URL.
34*216b518aSAndrew Jeffery
35*216b518aSAndrew Jeffery    Line comments are to be denoted "# SOME COMMENT" (typical shell style
36*216b518aSAndrew Jeffery    comment); it is important to follow the correct syntax and semantics as we
37*216b518aSAndrew Jeffery    may want to use automated tools with this file in the future.
38*216b518aSAndrew Jeffery
39*216b518aSAndrew Jeffery    A change cannot be added to an OpenBMC repository without a MAINTAINER's
40*216b518aSAndrew Jeffery    approval; thus, a MAINTAINER should always be listed as a reviewer.
41*216b518aSAndrew Jeffery
42*216b518aSAndrew JefferySTART OF MAINTAINERS LIST
43*216b518aSAndrew Jeffery-------------------------
44*216b518aSAndrew Jeffery
45*216b518aSAndrew JefferyM:  Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!>
46*216b518aSAndrew JefferyR:  Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!>
47