summaryrefslogtreecommitdiff
path: root/meta-hpe/MAINTAINERS
diff options
context:
space:
mode:
authorJorge Cisneros <jorge.cisneros@hpe.com>2020-08-28 23:03:44 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2020-09-09 16:48:46 +0300
commit4d14968af13ba43fb00d0a89a1ff4e18a8d25c69 (patch)
treeb4d4d622977aa68c87d39c3c174ef7610c09fa67 /meta-hpe/MAINTAINERS
parent914749fe544d9bb190c50b0dad4966a6ea98a068 (diff)
downloadopenbmc-4d14968af13ba43fb00d0a89a1ff4e18a8d25c69.tar.xz
Initial commit to support HPE DL360 POC servers.
Signed-off-by: Jorge Cisneros <jorge.cisneros@hpe.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com> Change-Id: I71fe33468398ca0b736fa5690c480a031a903d6a
Diffstat (limited to 'meta-hpe/MAINTAINERS')
-rw-r--r--meta-hpe/MAINTAINERS52
1 files changed, 52 insertions, 0 deletions
diff --git a/meta-hpe/MAINTAINERS b/meta-hpe/MAINTAINERS
new file mode 100644
index 000000000..96924fc67
--- /dev/null
+++ b/meta-hpe/MAINTAINERS
@@ -0,0 +1,52 @@
+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
+-------------------------
+
+# THIS REPOSITORY HAS A DIFFERENT SUBMISSION PROCESS: this is a subtree in
+# @openbmc and is synced by the maintainer using git-subtree. Please submit
+# changes against @openbmc.
+M: Gilbert Chen <gilbert.chen@hpe.com>
+M: John Chung <john.chung@hpe.com>
+M: Jorge Cisneros <jorge.cisneros@hpe.com>
+M: Mike Garrett <mike.garrett@hpe.com>
+M: Edward Newman <edward.newman@hpe.com>