Reword contributors page and update links

This patch adds clarifications and updates links around the contributors
page.

Author: Melanie Plageman <melanieplageman@gmail.com>

templates/contributors/list.html

@@ -5,8 +5,13 @@
 <h1>Contributor Profiles <i class="fa fa-users"></i></h1>
 <p>These are the fine people that make PostgreSQL what it is today!</p>
 
-<p>To suggest additions to the list, please email
+<p>To suggest additions to this list, please email the
-    <a href="mailto:contributors@postgresql.org">contributors@postgresql.org</a>.
+  <a href="/about/governance/contributors/">Contributors Committee</a> at
+  <a href="mailto:contributors@postgresql.org">contributors@postgresql.org</a>.
+    See the <a href="/about/policies/contributors/">Recognized Contributors</a>
+    policy for more information on becoming a recognized contributor.
+</p>
+<p>
     Existing contributors can update their information in their
     <a href="/account/profile/">user profile</a>.
 </p>

templates/pages/about/governance/contributors.html

@@ -9,12 +9,16 @@
   who decides on the status of each Contributor, or potential Contributor,
   on an individual basis. Decisions are made in accordance with the
   <a href="/about/policies/contributors/">Recognized Contributors</a> policy.
-  The decision of the committee is final unless overridden by the
+  The current method of choosing who qualifies as a Contributor is via simple
-  Core Team. The Contributor Committee strives to meet regularly to
+  majority vote of those on the committee. The decision of the committee is
-  discuss the current pool of candidates. The
+  final unless overridden by the Core Team.
-  <a href="/community/contributors/">Contributor Profiles</a> page is
+</p>
-  updated promptly after any decisions are made with respect to additions
+
-  or changes.
+<p>
+  The size and membership of the Committee is self determined,
+  but ratified by a simple majority vote of the Core Team. Generally
+  the goal is that there be a minimum of three people, with no single
+  company employing a majority of the committee membership.
 </p>
 
 <p>
@@ -27,10 +31,10 @@
 </ul>
 
 <p>
-  The size and membership of the Committee is self determined,
+  The Contributor Committee strives to meet regularly to
-  but ratified by a simple majority vote of the Core Team. Generally
+  discuss the current pool of candidates. The
-  the goal is that there be a minimum of three people, with no single
+  <a href="/community/contributors/">Contributor Profiles</a> page is
-  company employing a majority of the committee membership.
+  updated promptly after any decisions are made with respect to additions
+  or changes.
 </p>
-
 {%endblock%}

templates/pages/about/policies/contributors.html

@@ -6,11 +6,17 @@
 <h1>Recognized Contributors <i class="fas fa-gavel"></i></h1>
 
 <p>
-  The PostgreSQL <a href="/community/contributors/">Contributor Profiles</a> page
+  The PostgreSQL <a href="/community/contributors/">Contributor Profiles</a>
-  includes people who have made substantial, long-term contributions of time
+  page includes people who have made substantial, long-term contributions of
-  and effort to the PostgreSQL project. One-time-only or short-term contributions
+  time and effort to the PostgreSQL project. One-time-only or short-term
-  are not usually considered adequate for listing, unless they involve quite large
+  contributions are not usually considered adequate for listing, unless they
-  amounts of code and time. Financial contributions get listed on the
+  involve quite large amounts of code and time. For a list of all code
+  contributions to a specific release, see the
+  <a href="/docs/release/">Release Notes</a> for released versions of
+  PostgreSQL.
+</p>
+<p>
+  Financial contributions get listed on the
   <a href="/about/sponsors/">Sponsors</a> pages, not here.
 </p>
 
@@ -41,8 +47,9 @@
   period of time.
 </p>
 <ul>
-  <li>Hackers Emeritus - past Core Team members</li>
+  <li><strong>Past Major Contributors</strong>: previous Major Contributors and
-  <li>Past Contributors - all past Contributors (Major or otherwise)</li>
+    previous Core Team members</li>
+  <li><strong>Past Contributors</strong>: previous Contributors</li>
 </ul>
 
 <h2>Types of Contributions</h2>
@@ -75,16 +82,25 @@
       #postgresql IRC channel, Postgres slack channel, Stack Overflow
   </li>
 </ul>
-
+<p> If there is a type of contribution that you feel should be listed here or
-
+  expanded upon, email
-<h2>Committee Governance</h2>
+  <a href="mailto:contributors@postgresql.org">contributors@postgresql.org</a>.
-<p>
-  The current method of choosing who qualifies as a Contributor is via
-  simple majority vote of those on the committee. The size and membership
-  of the Committee is self determined, but ratified by a simple majority
-  vote of the Core Team. Generally the goal is that there be a minimum of
-  three people, with no single company employing a majority of the
-  committee membership.
 </p>
 
+
+<h2>Contributors Committee Governance</h2>
+<p>
+  The governance of the 
+  <a href="/about/governance/contributors/">Contributors Committee</a> is
+  described on the <a href="/about/governance/contributors/">Contributors Committee</a>
+  page.
+</p>
+
+<h2>Nominating New Recognized Contributors</h2>
+<p>
+  If there is a PostgreSQL contributor who you think is making sustained
+  contributions of the type described here, email a description of their
+  contributions to
+  <a href="mailto:contributors@postgresql.org">contributors@postgresql.org</a>.
+</p>
 {%endblock%}