community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgard...@apache.org
Subject svn commit: r790358 - in /websites/production/community: ./ content/committers/index.html content/newcommitter.html
Date Wed, 01 Jun 2011 23:59:41 GMT
Author: rgardler
Date: Wed Jun  1 23:59:40 2011
New Revision: 790358

Log:
Publishing merge to community site by rgardler

Modified:
    websites/production/community/   (props changed)
    websites/production/community/content/committers/index.html
    websites/production/community/content/newcommitter.html

Propchange: websites/production/community/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Jun  1 23:59:40 2011
@@ -1,2 +1,2 @@
 /websites/staging/comdev/trunk:779592-779702
-/websites/staging/community/trunk:779703-790351
+/websites/staging/community/trunk:779703-790357

Modified: websites/production/community/content/committers/index.html
==============================================================================
--- websites/production/community/content/committers/index.html (original)
+++ websites/production/community/content/committers/index.html Wed Jun  1 23:59:40 2011
@@ -111,8 +111,8 @@ projects are required to follow – t
 <a href="http://www.apache.org/dev/release.html">release voting</a>, <a href="http://www.apache.org/legal/">legal
policy</a>, <a href="http://www.apache.org/foundation/marks/">brand policy</a>,

 using <a href="http://www.apache.org/dev/#mail">mailing lists</a>, etc., which
are <a href="https://blogs.apache.org/comdev/entry/what_makes_apache_projects_different">documented
in various places</a>. </p>
 <p>One of these invariant rules is that projects are managed and used
-independently of any commercial interests. The goal is to createan 
-environemnt in which all participants are equal and thus have an equal
+independently of any commercial interests. The goal is to create an 
+environment in which all participants are equal and thus have an equal
 opportunity to contribute to and benefit from our software, regardless
 of motivation or financial objectives. This is discussed in more detail
 in our document <a href="/projectIndependence.html">Project Independence</a>.</p>
@@ -125,8 +125,8 @@ project. This section describes some of 
 with. In most cases you will need to be a committer to carry out these
 activities, although non-committers can often act in supporting roles.</p>
 <ul>
+<li><a href="/newcommitter.html">Assessing and approving new committers</a></li>
 <li><a href="/boardreport.html">Board Reports</a></li>
-<li><a href="/newcommitter.html">New Committer Handling</a></li>
 </ul>
                          </DIV>
                      </DIV>

Modified: websites/production/community/content/newcommitter.html
==============================================================================
--- websites/production/community/content/newcommitter.html (original)
+++ websites/production/community/content/newcommitter.html Wed Jun  1 23:59:40 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
fuidelines</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



Mime
View raw message