Author: julianfoad
Date: Mon Nov 13 17:15:36 2017
New Revision: 1815120
URL: http://svn.apache.org/viewvc?rev=1815120&view=rev
Log:
* staging: Catch-up merge from 'publish'.
Modified:
subversion/site/staging/ (props changed)
subversion/site/staging/docs/community-guide/roles.part.html
Propchange: subversion/site/staging/
------------------------------------------------------------------------------
svn:mergeinfo = /subversion/site/publish:1812681-1815119
Modified: subversion/site/staging/docs/community-guide/roles.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/roles.part.html?rev=1815120&r1=1815119&r2=1815120&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/roles.part.html (original)
+++ subversion/site/staging/docs/community-guide/roles.part.html Mon Nov 13
17:15:36 2017
@@ -83,10 +83,13 @@ list</a> might be the most convenient pl
<p>A full committer sponsors the partial committer. Usually this
means the full committer has applied several patches to the same area
from the proposed partial committer, and realizes things would be
-easier if the person were just committing directly. Approval is not
-required from the full committers; it is assumed that sponsors know
-what they're doing and will watch the partial committer's first few
-commits to make sure everything's going smoothly.</p>
+easier if the person were just committing directly. It is customary and
+recommended for the sponsor to float the prospect by private@ before
+issueing an invitation, but not required; sponsors are trusted to use
+good judgement.</p>
+
+<p>The sponsor watches the partial committer's first few commits to ensure
+everything's going smoothly.</p>
<p>Patches submitted by a partial committer may be committed by that
committer even if they are outside that person's domain. This
