diff --git a/Documentation/dev-processes.txt b/Documentation/dev-processes.txt
index c0a6cf773c..b3c147fe54 100644
--- a/Documentation/dev-processes.txt
+++ b/Documentation/dev-processes.txt
@@ -28,6 +28,9 @@ The steering committee has 5 members:
 * 2 non-Google maintainers, elected by non-Google maintainers for the
   period of 1 year (see link:#steering-committee-election[below])
 
+Refer to the project homepage for the link:https://www.gerritcodereview.com/esc.html[
+list of current committee members].
+
 The steering committee should act in the interest of the Gerrit project
 and the whole Gerrit community.
 
diff --git a/Documentation/dev-roles.txt b/Documentation/dev-roles.txt
index 9007aa3746..5f411448be 100644
--- a/Documentation/dev-roles.txt
+++ b/Documentation/dev-roles.txt
@@ -136,7 +136,9 @@ maintainers].
 == Maintainer
 
 Maintainers are the gatekeepers of the project and are in charge of
-approving and submitting changes.
+approving and submitting changes. Refer to the project homepage for
+the link:https://www.gerritcodereview.com/maintainers.html[
+list of current maintainers].
 
 Maintainers should only approve changes that:
 
@@ -227,7 +229,9 @@ The Gerrit project has an Engineering Steering Committee (ESC) that
 governs the project, see link:dev-processes.html#project-governance[Project Governance].
 
 Members of the steering committee are expected to act in the interest
-of the Gerrit project and the whole Gerrit community.
+of the Gerrit project and the whole Gerrit community. Refer to the project
+homepage for the link:https://www.gerritcodereview.com/esc.html[
+list of current committee members].
 
 For those that are familiar with scrum, the steering committee member
 role is similar to the role of an agile product owner.