Author: buildbot
Date: Wed Jun  1 23:41:58 2011
New Revision: 790357

Log:
Staging update by buildbot

Modified:
    websites/staging/community/trunk/content/newcommitter.html

Modified: websites/staging/community/trunk/content/newcommitter.html
==============================================================================
--- websites/staging/community/trunk/content/newcommitter.html (original)
+++ websites/staging/community/trunk/content/newcommitter.html Wed Jun  1 
23:41:58 2011
@@ -104,14 +104,14 @@
                           <p>Identifying potential new commiters, calling a 
vote for their recognition
 as a committer and processing the relevant documents is something that the
 whole community can contribute to.</p>
-<p>Each project has different approches to managing new committers, this page
+<p>Each project has different appraoches to managing new committers, this page
 describes a common process found in many Apache projects. It also provides
 drafts for the various communications that are necessary.</p>
 <p><a 
name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a></p>
 <h1 id="guidelines_for_assessing_new_candidates_for_committership">Guidelines 
for assessing new candidates for committership</h1>
 <p>When voting, all PMC members need to make up your own mind, perhaps search
 mailing lists and Jira, etc. The following are some tips that we developed.
-Also consider the Apache Forrest <a 
href="http://forrest.apache.org/committed.html";>committer guidelines</a></p>
+Also consider the Apache Forrest <a 
href="http://forrest.apache.org/committed.html";>committer guidelines</a>.</p>
 <p><a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a></p>
 <h2 id="ability_to_work_co-operatively_with_peers">Ability to work 
co-operatively with peers.</h2>
 <p>How do we evaluate?  By the interactions they have through mail. By how
@@ -121,7 +121,7 @@ process.</p>
 <h2 id="ability_to_be_a_mentor">Ability to be a mentor.</h2>
 <p>How do we evaluate?  By the interactions they have through mail. By how
 clear they are and how willing they are to point at appropriate background
-materials (or event create them).</p>
+materials (or even create them).</p>
 <p><a name="NewCommitter-Community"></a></p>
 <h2 id="community">Community</h2>
 <p>How do we evaluate?  By the interactions they have through mail.</p>
@@ -131,11 +131,9 @@ materials (or event create them).</p>
 on not-so-fun tasks as well.</p>
 <p><a name="NewCommitter-Personalskill/ability"></a></p>
 <h2 id="personal_skillability">Personal skill/ability</h2>
-<ol>
-<li>How do we evaluate?  A solid general understanding of the project. 
+<p>How do we evaluate?  A solid general understanding of the project. 
 Quality of discussion in mail.  Patches easy to apply with only
-a cursory review.</li>
-</ol>
+a cursory review.</p>
 <p><a name="NewCommitter-NewCommitterProcess"></a></p>
 <h1 id="new_committer_process">New Committer Process</h1>
 <p>This section describes a typical Apache projects process for handling the


Reply via email to