svn commit: r50326 - head/en_US.ISO8859-1/htdocs/internal

Wed Jun 7 15:02:44 UTC 2017

Author: gjb
Date: Wed Jun  7 15:02:43 2017
New Revision: 50326
URL: https://svnweb.freebsd.org/changeset/doc/50326

Log:
  Whitespace cleanup and line wrapping.
  
  Translators please ignore.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  head/en_US.ISO8859-1/htdocs/internal/members.xml

Modified: head/en_US.ISO8859-1/htdocs/internal/members.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/internal/members.xml	Wed Jun  7 14:57:00 2017	(r50325)
+++ head/en_US.ISO8859-1/htdocs/internal/members.xml	Wed Jun  7 15:02:43 2017	(r50326)
@@ -14,9 +14,9 @@
   <body class="navinclude.docs">
 
     <h1>FreeBSD Project Members</h1>
-    
+
     <p>A FreeBSD Project Member is an individual who has made a
-      notable contribution to the FreeBSD Project. That may be in the
+      notable contribution to the FreeBSD Project.  That may be in the
       form of new code, documentation, or patches to existing code and
       documentation, or in other ways that the Core Team designates,
       including community management and advocacy.</p>
@@ -26,12 +26,12 @@
     <p>Committers are those Project members who have been granted
       commit access (a "commit bit") to one or more of the Project's
       repositories.</p>
-      
+
     <h2>Member Benefits:</h2>
 
     <ul>
       <li>an @freebsd.org email address which also gives them regular
-        Bugzilla and Phabricator logins</li>
+	Bugzilla and Phabricator logins</li>
       <li>permission to assign bugs to themselves in bugzilla</li>
       <li>access to freefall and the universe build machines</li>
       <li>access to the test clusters</li>
@@ -52,11 +52,11 @@
     <ul>
       <li>adheres to the Project's standards and practices.</li>
       <li>is correctly attributed to its authors.</li>
-      <li>has appropriate licensing.  Where this is the original
-        work of the Project Member, the standard FreeBSD license is
-        preferred.</li>
+      <li>has appropriate licensing.  Where this is the original work
+	of the Project Member, the standard FreeBSD license is
+	preferred.</li>
     </ul>
-    
+
     <p>Members MUST create SSH and PGP keys in order to gain access to
       Project resources.</p>
 
@@ -79,12 +79,13 @@
     <h2>FAQ:</h2>
 
     <dl>
-      <dt>Is a mentor assigned to each newly created Project Member?</dt>
+      <dt>Is a mentor assigned to each newly created Project
+	Member?</dt>
       <dd>Project Members are only assigned a mentor if they become
-        a committer, or if they have a commit bit reactivated after a
-        significant period of inactivity.  This only applies to
-        Committers since the primary purpose of a mentor is to review
-        what the mentee intends to commit.</dd>
+	a committer, or if they have a commit bit reactivated after
+	a significant period of inactivity.  This only applies to
+	Committers since the primary purpose of a mentor is to review
+	what the mentee intends to commit.</dd>
       <dd>No such formal arrangement is required when someone is
 	made into an ordinary Project Member, but it is expected that
 	the people that sponsor a new Member will assist them with
@@ -93,20 +94,19 @@
       <dt>Do you have to become an Ordinary Member before you can be
 	granted a commit bit?</dt>
       <dd>No.  There is no requirement for prospective Committers to
-        have spent time as Ordinary Members.  However it is
-        anticipated that this will become a common practice as part of
-        the route towards committer-hood.</dd>
+	have spent time as Ordinary Members.  However it is
+	anticipated that this will become a common practice as part of
+	the route towards committer-hood.</dd>
       <dt>Do Committers who have given up their commit bits
-        effectively become just Ordinary Members?</dt>
+	effectively become just Ordinary Members?</dt>
       <dd>All Committers are Project members, but former Committers
 	are considered Committer Alumni.  Alumni may revert back to
 	active Committers simply by requesting reinstatement of their
 	commit access.</dd>
       <dt>How does this affect the existing 3rd Party Developer
-        status?</dt>
-      <dd>Existing 3rd Party Developers will be promoted to
-        Project Members.</dd>
+	status?</dt>
+      <dd>Existing 3rd Party Developers will be promoted to Project
+	Members.</dd>
     </dl>
-    
   </body>
 </html>
