OWNERS: switch references from MAINTAINERS

MAINTAINERS files are now deprecated and/or removed and replaced by OWNERS. Update the documentation accordingly. Signed-off-by: Patrick Williams <[email protected]> Change-Id: I9c7e6ca3aeb41ea8f92ddc42072252d4f65de0aa
openbmc · Aug 4, 2022 · 91f5177 · 91f5177
1 parent 7d09203
commit 91f5177
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -334,8 +334,8 @@ your reviews from the [OpenBMC Gerrit server](https://gerrit.openbmc.org) search
 or menu (All > Open, or My > Changes).
 
 Invite reviewers to review your changes.  Each OpenBMC repository has
-a `MAINTAINERS` file that lists required reviewers who are subject
-matter experts.  Those reviewers may add additional reviewers.  To add
+an `OWNERS` file that lists required reviewers who are subject matter
+experts.  Those reviewers may add additional reviewers.  To add
 reviewers from the Gerrit web page, click the "add reviewers" icon by
 the list of reviewers.
 
@@ -418,7 +418,7 @@ than yours. Do everything you can to make it easy for the reviewer to review
 your contribution.
 
 If you feel your patch has been missed entirely, of course, it's
-alright to email the maintainers (addresses available in MAINTAINERS file) or
+alright to email the maintainers (addresses available in OWNERS file) or
 ping them on Discord - but a reasonable timeframe to do so is on the order of a
 week, not on the order of hours.
 

diff --git a/development/gerrit-setup.md b/development/gerrit-setup.md
@@ -84,7 +84,7 @@ will look like.
 * Push your changes to Gerrit for code review:
   `git push origin HEAD:refs/for/master`
 * Go to [Gerrit web interface](https://gerrit.openbmc.org/), click on
-  your new review, and add reviewers based on `MAINTAINERS` file in the repo.
+  your new review, and add reviewers based on `OWNERS` file in the repo.
 
 ##### Conclusion
 If you've completed all of the above steps successfully, that's it! You have now