summaryrefslogtreecommitdiff
path: root/meta-asrock
diff options
context:
space:
mode:
authorZev Weiss <zev@bewilderbeest.net>2021-09-16 00:45:26 +0300
committerPatrick Williams <patrick@stwcx.xyz>2022-01-05 18:39:15 +0300
commit13b40bb521a6fd8f9ce2119ac177183abc8659cf (patch)
treea59d18fe659ad1818e7a4e53441f91dce15bf8d1 /meta-asrock
parent4d79a2543e1e8b4c7e1ad65a99f97a75700f00d7 (diff)
downloadopenbmc-13b40bb521a6fd8f9ce2119ac177183abc8659cf.tar.xz
meta-asrock: Add Zev Weiss as maintainer
Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: I9c224ea0de69ea378732f40f3b4d9fe8964360b0
Diffstat (limited to 'meta-asrock')
-rw-r--r--meta-asrock/MAINTAINERS45
-rw-r--r--meta-asrock/OWNERS2
2 files changed, 47 insertions, 0 deletions
diff --git a/meta-asrock/MAINTAINERS b/meta-asrock/MAINTAINERS
new file mode 100644
index 0000000000..ae85d8344b
--- /dev/null
+++ b/meta-asrock/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> <DISCORD_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> <DISCORD_USERNAME!>;
+ if omitted from an entry, assume one of the maintainers from the
+ MAINTAINERS entry.
+ R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_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: Zev Weiss <zev@bewilderbeest.net> <zevweiss!>
diff --git a/meta-asrock/OWNERS b/meta-asrock/OWNERS
new file mode 100644
index 0000000000..70a4c8bc38
--- /dev/null
+++ b/meta-asrock/OWNERS
@@ -0,0 +1,2 @@
+owners:
+- zev@bewilderbeest.net