Mailing-List: contact cvs-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: johndament@apache.org
To: cvs@incubator.apache.org
Date: Thu, 03 Aug 2017 10:37:48 -0000
Message-Id: <90e6490ed00544678357d84cde210a70@git.apache.org>
Subject: [1/2] incubator git commit: Clarify the email format.
archived-at: Thu, 03 Aug 2017 10:37:51 -0000

Repository: incubator
Updated Branches:
  refs/heads/master 2d717a53b -> 15abc3381


Clarify the email format.


Project: http://git-wip-us.apache.org/repos/asf/incubator/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator/commit/cafb0259
Tree: http://git-wip-us.apache.org/repos/asf/incubator/tree/cafb0259
Diff: http://git-wip-us.apache.org/repos/asf/incubator/diff/cafb0259

Branch: refs/heads/master
Commit: cafb025932f2630d40cfaa35b5e98a6076a8350c
Parents: 2d717a5
Author: John D. Ament <johndament@apache.org>
Authored: Thu Aug 3 06:37:25 2017 -0400
Committer: John D. Ament <johndament@apache.org>
Committed: Thu Aug 3 06:37:25 2017 -0400

----------------------------------------------------------------------
 assets/guides/ppmc-offer.txt | 58 +++++++++++++++++++++++++++++++++++++++
 pages/guides/ppmc-offer.txt  | 58 ---------------------------------------
 pages/guides/ppmc.ad         |  6 ++--
 3 files changed, 62 insertions(+), 60 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator/blob/cafb0259/assets/guides/ppmc-offer.txt
----------------------------------------------------------------------
diff --git a/assets/guides/ppmc-offer.txt b/assets/guides/ppmc-offer.txt
new file mode 100644
index 0000000..27b8978
--- /dev/null
+++ b/assets/guides/ppmc-offer.txt
@@ -0,0 +1,58 @@
+Dear Joe Bob
+
+In recognition of your demonstrated commitment to, and alignment with, the
+goals of the Apache Frizzle project, the Frizzle PPMC has voted to offer you
+membership in the Frizzle PPMC ("Podling Project Management Committee").
+
+Please let us know if you accept by subscribing to the private alias [by
+sending mail to private-subscribe@frizzle.incubator.apache.org], and posting 
+a message to private@frizzle.incubator.apache.org.
+
+The PPMC is the Incubator podling version of a project PMC ("Project
+Management Committee") that for every top-level project is tasked by the
+Apache Board of Directors with official oversight and binding votes in
+that project.  When Frizzle graduates from the Incubator to a top-level
+project, the project PMC is usually formed from the membership of the PPMC.
+Note that while participation in the PMC after graduation is not
+guaranteed, simply continuing your constructive and active participation
+is usually sufficient.
+
+As a PPMC member, and later as a PMC member, you are responsible for
+continuing the general project, code, and community oversight that you
+have exhibited so far.  The votes of the PPMC are not legally binding;
+votes of the Incubator PMC are.  However, many of the PPMC members
+are also Incubator PMC members, so they implicitly cast binding votes
+when we vote on PPMC issues.  While this is an important legal
+distinction, it shouldn't enter your thinking when working on the PPMC -
+members should treat every decision as if it were legally binding for the ASF.  
+Also, in day-to-day activities, the Incubator PMC member vs PPMC member
+distinction should be invisible -- we are peers.
+
+All PPMC members are subscribed to the project's private mail list, which 
+is used to discuss issues unsuitable for an open, public forum, such as
+people issues (e.g. new committers, problematic community members, etc.),
+security issues, and the like.  It can't be emphasized enough that
+care should be taken to minimize the use of the private list, discussing
+everything possible on the appropriate public list.
+
+The private PPMC list is *private* - it is strictly for the use of the
+PPMC. Messages are not to be forwarded to anyone else without the express
+permission of the PPMC. Also note that any Member of the Foundation has
+the right to review and participate in any PPMC or PMC list, as a PMC 
+and PPMC are acting on behalf of the Membership.
+
+Finally, the PPMC (and assuming graduation, the PMC) is not meant to create 
+a hierarchy within the committership or the community.  In fact, a goal is to
+add all committers over time to the PPMC/PMC, as our belief is that those who
+do the work should get a binding vote.  Therefore, in our day-to-day
+interactions with the rest of the community, we continue to interact as
+peers, where every reasonable opinion is considered, and all community
+members are invited to participate in our public voting.  If there ever
+is a situation where the PMC/PPMC's view differs significantly from that 
+of the rest of the community, this is a symptom of a problem that needs to
+be addressed.
+
+With the expectation of your acceptance, welcome!
+
+The Apache Frizzle PPMC
+

http://git-wip-us.apache.org/repos/asf/incubator/blob/cafb0259/pages/guides/ppmc-offer.txt
----------------------------------------------------------------------
diff --git a/pages/guides/ppmc-offer.txt b/pages/guides/ppmc-offer.txt
deleted file mode 100644
index 27b8978..0000000
--- a/pages/guides/ppmc-offer.txt
+++ /dev/null
@@ -1,58 +0,0 @@
-Dear Joe Bob
-
-In recognition of your demonstrated commitment to, and alignment with, the
-goals of the Apache Frizzle project, the Frizzle PPMC has voted to offer you
-membership in the Frizzle PPMC ("Podling Project Management Committee").
-
-Please let us know if you accept by subscribing to the private alias [by
-sending mail to private-subscribe@frizzle.incubator.apache.org], and posting 
-a message to private@frizzle.incubator.apache.org.
-
-The PPMC is the Incubator podling version of a project PMC ("Project
-Management Committee") that for every top-level project is tasked by the
-Apache Board of Directors with official oversight and binding votes in
-that project.  When Frizzle graduates from the Incubator to a top-level
-project, the project PMC is usually formed from the membership of the PPMC.
-Note that while participation in the PMC after graduation is not
-guaranteed, simply continuing your constructive and active participation
-is usually sufficient.
-
-As a PPMC member, and later as a PMC member, you are responsible for
-continuing the general project, code, and community oversight that you
-have exhibited so far.  The votes of the PPMC are not legally binding;
-votes of the Incubator PMC are.  However, many of the PPMC members
-are also Incubator PMC members, so they implicitly cast binding votes
-when we vote on PPMC issues.  While this is an important legal
-distinction, it shouldn't enter your thinking when working on the PPMC -
-members should treat every decision as if it were legally binding for the ASF.  
-Also, in day-to-day activities, the Incubator PMC member vs PPMC member
-distinction should be invisible -- we are peers.
-
-All PPMC members are subscribed to the project's private mail list, which 
-is used to discuss issues unsuitable for an open, public forum, such as
-people issues (e.g. new committers, problematic community members, etc.),
-security issues, and the like.  It can't be emphasized enough that
-care should be taken to minimize the use of the private list, discussing
-everything possible on the appropriate public list.
-
-The private PPMC list is *private* - it is strictly for the use of the
-PPMC. Messages are not to be forwarded to anyone else without the express
-permission of the PPMC. Also note that any Member of the Foundation has
-the right to review and participate in any PPMC or PMC list, as a PMC 
-and PPMC are acting on behalf of the Membership.
-
-Finally, the PPMC (and assuming graduation, the PMC) is not meant to create 
-a hierarchy within the committership or the community.  In fact, a goal is to
-add all committers over time to the PPMC/PMC, as our belief is that those who
-do the work should get a binding vote.  Therefore, in our day-to-day
-interactions with the rest of the community, we continue to interact as
-peers, where every reasonable opinion is considered, and all community
-members are invited to participate in our public voting.  If there ever
-is a situation where the PMC/PPMC's view differs significantly from that 
-of the rest of the community, this is a symptom of a problem that needs to
-be addressed.
-
-With the expectation of your acceptance, welcome!
-
-The Apache Frizzle PPMC
-

http://git-wip-us.apache.org/repos/asf/incubator/blob/cafb0259/pages/guides/ppmc.ad
----------------------------------------------------------------------
diff --git a/pages/guides/ppmc.ad b/pages/guides/ppmc.ad
index 6868310..a6b7834 100644
--- a/pages/guides/ppmc.ad
+++ b/pages/guides/ppmc.ad
@@ -190,10 +190,10 @@ the vote result's message id of the following form:
 --
 To: private at incubator.apache.org
 CC: private at PODLING.incubator.apache.org
-Subject: [NOTICE] *Joe Bob* for Podling PPMC
+Subject: [NOTICE] Joe Bob for PODLING PPMC
 Body:
 
-Joe Bob has been voted as a new member of the Podling PPMC. the vote thread is at: *link to the vote thread*
+Joe Bob has been voted as a new member of the *PODLING* PPMC. the vote thread is at: *link to the vote thread*
 --
 
 *It should noted that there is a grace period of 72 hours from when the
@@ -202,6 +202,8 @@ is formally invited. This is an important part of the overall
 process. Failure to do this can result in an embarassing situation
 for people involved.*
 
+In the email you send, replace *PODLING* with your podling's actual name, and replace Joe Bob with the prospect's actual name.
+
 After 72 hours, Joe Bob
 should be invited to join the PPMC, using a sample message like
 link:ppmc-offer.txt[this].


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org