summaryrefslogtreecommitdiffstats
path: root/meta-ibm
diff options
context:
space:
mode:
authorBrad Bishop <bradleyb@fuzziesquirrel.com>2018-09-26 13:40:35 -0400
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-09-27 22:08:11 -0400
commit25b3e4f4db224aaf178508a2ae1dd1d3803982f8 (patch)
tree20a4f22624ff8fe9bec8f92ed32a6d696e20ed47 /meta-ibm
parentc8267c3a9c09abf38cad806c5690d19346735eac (diff)
downloadtalos-openbmc-25b3e4f4db224aaf178508a2ae1dd1d3803982f8.tar.gz
talos-openbmc-25b3e4f4db224aaf178508a2ae1dd1d3803982f8.zip
meta-ibm: Add maintainers file
Add a maintainers file for the meta-ibm layer. (From meta-ibm rev: 4d3b4f9f4f97de48359babe51bd1db744a534e31) Change-Id: Ib88d52459f1b540db21e9e90c08bee5351f013b9 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-ibm')
-rw-r--r--meta-ibm/MAINTAINERS45
1 files changed, 45 insertions, 0 deletions
diff --git a/meta-ibm/MAINTAINERS b/meta-ibm/MAINTAINERS
new file mode 100644
index 000000000..bfe81dea1
--- /dev/null
+++ b/meta-ibm/MAINTAINERS
@@ -0,0 +1,45 @@
+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!>
OpenPOWER on IntegriCloud