diff options
author | Andrew Jeffery <andrew@aj.id.au> | 2018-05-19 02:26:38 +0930 |
---|---|---|
committer | Ratan Gupta <ratagupt@linux.vnet.ibm.com> | 2018-05-22 05:15:17 +0000 |
commit | 3c166b39a5f5737de57b4543cddc3f0700e88d63 (patch) | |
tree | 6db54556780cf93b2ef9dfd0cf29faf4e4f61673 | |
parent | 1f5a002f4b596522cf46eaad3cfd072a44b5848d (diff) | |
download | phosphor-user-manager-3c166b39a5f5737de57b4543cddc3f0700e88d63.tar.gz phosphor-user-manager-3c166b39a5f5737de57b4543cddc3f0700e88d63.zip |
Add MAINTAINERS file
Change-Id: I1e43c36c5590b95243bde0feeb04e3b525f9e88a
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
-rw-r--r-- | MAINTAINERS | 46 |
1 files changed, 46 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index 0000000..b4d8704 --- /dev/null +++ b/MAINTAINERS @@ -0,0 +1,46 @@ +How to use this list: + Find the most specific section entry (described below) that matches where + your change lives and add the reviewers (R) and maintainers (M) as + reviewers. You can use the same method to track down who knows a particular + code base best. + + Your change/query may span multiple entries; that is okay. + + If you do not find an entry that describes your request at all, someone + forgot to update this list; please at least file an issue or send an email + to a maintainer, but preferably you should just update this document. + +Description of section entries: + + Section entries are structured according to the following scheme: + + X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!> + X: ... + . + . + . + + Where REPO_NAME is the name of the repository within the OpenBMC GitHub + organization; FILE_PATH is a file path within the repository, possibly with + wildcards; X is a tag of one of the following types: + + M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; + if omitted from an entry, assume one of the maintainers from the + MAINTAINERS entry. + R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>; + these people are to be added as reviewers for a change matching the repo + path. + F: Denotes forked from an external repository; has fields URL. + + Line comments are to be denoted "# SOME COMMENT" (typical shell style + comment); it is important to follow the correct syntax and semantics as we + may want to use automated tools with this file in the future. + + A change cannot be added to an OpenBMC repository without a MAINTAINER's + approval; thus, a MAINTAINER should always be listed as a reviewer. + +START OF MAINTAINERS LIST +------------------------- + +M: Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!> +R: Ratan Gupta <ratagupt@linux.vnet.ibm.com> <rgupta!> |