Move to an OWNERS file
The MAINTAINERS file as been deprecated in favor of OWNERS, so make the
switch.
Change-Id: I2b27728c1b91ff14b42e3e8d2738dd9b4a2fabf5
Signed-off-by: Jason M. Bills <jason.m.bills@intel.com>
diff --git a/MAINTAINERS b/MAINTAINERS
deleted file mode 100644
index 15655ad..0000000
--- a/MAINTAINERS
+++ /dev/null
@@ -1,45 +0,0 @@
-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!>
diff --git a/OWNERS b/OWNERS
new file mode 100644
index 0000000..f1655c2
--- /dev/null
+++ b/OWNERS
@@ -0,0 +1,44 @@
+# OWNERS
+# ------
+#
+# The OWNERS file maintains the list of individuals responsible for various
+# parts of this repository, including code review and approval. We use the
+# Gerrit 'owners' plugin, which consumes this file, along with some extra
+# keywords for our own purposes and tooling.
+#
+# For details on the configuration used by 'owners' see:
+# https://gerrit.googlesource.com/plugins/owners/+/refs/heads/master/owners/src/main/resources/Documentation/config.md
+#
+# An OWNERS file must be in the root of a repository but may also be present
+# in any subdirectory. The contents of the subdirectory OWNERS file are
+# combined with parent directories unless 'inherit: false' is set.
+#
+# The owners file is YAML and has [up to] 4 top-level keywords.
+# * owners: A list of individuals who have approval authority on the
+# repository.
+#
+# * reviewers: A list of individuals who have requested review notification
+# on the repository.
+#
+# * matchers: A list of specific file/path matchers for granular 'owners' and
+# 'reviewers'. See 'owners' plugin documentation.
+#
+# * openbmc: A list of openbmc-specific meta-data about owners and reviewers.
+# - name: preferred name of the individual.
+# - email: preferred email address of the individual.
+# - discord: Discord nickname of the individual.
+#
+# It is expected that these 4 sections will be listed in the order above and
+# data within them will be kept sorted.
+
+owners:
+- vernon.mauery@linux.intel.com
+
+reviewers:
+
+matchers:
+
+openbmc:
+- name: Vernon Mauery
+ email: vernon.mauery@linux.intel.com
+ discord: vmauery