summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Jeffery <andrew@aj.id.au>2018-05-19 01:03:59 +0930
committerRatan Gupta <ratagupt@linux.vnet.ibm.com>2018-05-19 08:33:56 +0000
commita37002fa0563b8136f3325ef19d5ec42aff2384d (patch)
tree9bf7087e91f526f03815b065e68d6af681e5d1f6
parentc19c054c01b7a42c24cdf38a270b33f56290abf3 (diff)
downloadipmi-fru-parser-a37002fa0563b8136f3325ef19d5ec42aff2384d.zip
ipmi-fru-parser-a37002fa0563b8136f3325ef19d5ec42aff2384d.tar.gz
Add MAINTAINERS file
Change-Id: Ife70429d13a77396c0ed1d3baca0e19a8ddb339f Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
-rw-r--r--MAINTAINERS48
1 files changed, 48 insertions, 0 deletions
diff --git a/MAINTAINERS b/MAINTAINERS
new file mode 100644
index 0000000..8d40665
--- /dev/null
+++ b/MAINTAINERS
@@ -0,0 +1,48 @@
+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: Vernon Mauery <vernon.mauery@linux.intel.com> <vmauery!>
+M: Tom Joseph <tomjose@linux.vnet.ibm.com> <tomjoseph!>
+M: Emily Shaffer <emilyshaffer@google.com> <emilyshaffer!>
+R: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
OpenPOWER on IntegriCloud