- Extend the commit bit expiration policy with a paragraph on suspending

cluster accounts

Approved by:	core
With hat:	core-secretary

en_US.ISO8859-1/htdocs/internal/expire-bits.xml

@@ -23,16 +23,25 @@
     procedural questions regarding the degree to which contact information
     and access methods for the account are maintainable.  For these
     reasons, the FreeBSD Core Team approved the following commit bit
-    expiration policy, which was posted to the Developers mailing list
-    on February 22, 2002, and later on October 30, 2013.</p>
+    expiration policy, last updated on November 26, 2013.</p>
 
   <h2>Policy</h2>
 
   <p>Committers that have not made a commit in 18 months may be removed
     from the access file from time to time.  Committers that wish to get
     back their commit bits will have to reapply with the appropriate
-    authority.  Future refinements to this policy may be forthcoming.</p>
-
+    authority.</p>
 
+  <p>If all of a committer's commit bits expire, then the committer's
+    <tt>FreeBSD.org</tt> account may also be suspended at the &os; Core
+    Team's discretion.  An account is suspended by disabling login
+    access and any other services (such as CGI scripts or non-trivial
+    mail forwarding configurations) that execute under the committer's
+    account.  Simple mail forwarding will continue to work, and an
+    individual may e-mail <tt>core@FreeBSD.org</tt> to update mail
+    forwarding settings.  The committer's files may or may not be
+    preserved at the &os; Core Team's discretion.  A suspended account
+    will be reactivated if any of a committer's commit bits are
+    restored.</p>
   </body>
 </html>