diff --git a/MAINTAINERS b/MAINTAINERS
deleted file mode 100644
index 3f29a53..0000000
--- a/MAINTAINERS
+++ /dev/null
@@ -1,46 +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:  Jeremy Kerr <jk@ozlabs.org> <jk!>
-R:  Brad Bishop <bradleyb@fuzziesquirrel.com> <radsquirrel!>
diff --git a/OWNERS b/OWNERS
deleted file mode 100644
index 78fcbfd..0000000
--- a/OWNERS
+++ /dev/null
@@ -1,48 +0,0 @@
-# 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.
-#
-#   * matches: A list of specific file/path matches 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:
-- jk@ozlabs.org
-
-reviewers:
-- bradleyb@fuzziesquirrel.com
-
-matches:
-
-openbmc:
-- name: Brad Bishop
-  email: bradleyb@fuzziesquirrel.com
-  discord: radsquirrel
-- name: Jeremy Kerr
-  email: jk@ozlabs.org
-  discord: jk-
diff --git a/README.md b/README.md
index 36012f9..f74b7ce 100644
--- a/README.md
+++ b/README.md
@@ -1,17 +1,7 @@
-rest-dbus: web interface to a dbus API
+# rest-dbus
 
-Losely based on https://github.com/joshtronic/python-dbus-rest-server.
-
-Includes code from the following projects:
-
-jQuery
- - http://jquery.com/
- - Released under the MIT license
-
-jsTree plugin for jQuery
- - http://jstree.com/
- - Released under the MIT license
-
-JsRender
- - http://jsviews.com/
- - Released under the MIT license
+rest-dbus was a [dfeet](https://wiki.gnome.org/Apps/DFeet)-like UI over HTTP
+written for OpenBMC.  It is no longer maintained and depends on Python 2, so
+you should probably not use it.  A port to the
+[bmcweb](https://github.com/openbmc/bmcweb) project implemented the same REST
+APIs as rest-dbus, but browser side support remains unimplemented.