incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject incubator git commit: Automatic Site Publish by git-site-role
Date Thu, 03 Aug 2017 10:39:05 GMT
Repository: incubator
Updated Branches:
  refs/heads/asf-site e317f8c8d -> 934da988a

Automatic Site Publish by git-site-role


Branch: refs/heads/asf-site
Commit: 934da988ab9aea5fae70713eb3d375ae8d48d398
Parents: e317f8c
Author: jenkins <>
Authored: Thu Aug 3 10:39:03 2017 +0000
Committer: jenkins <>
Committed: Thu Aug 3 10:39:03 2017 +0000

 content/feed.xml              |  4 +--
 content/guides/ppmc-offer.txt | 58 ++++++++++++++++++++++++++++++++++++++
 content/guides/ppmc.html      |  7 +++--
 content/sitemap.xml           |  2 +-
 4 files changed, 66 insertions(+), 5 deletions(-)
diff --git a/content/feed.xml b/content/feed.xml
index 4f1e8ec..762322b 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -6,8 +6,8 @@
     <atom:link href="" rel="self" type="application/rss+xml"
     <description>JBake Bootstrap Template</description>
-    <pubDate>Wed, 2 Aug 2017 23:46:50 +0000</pubDate>
-    <lastBuildDate>Wed, 2 Aug 2017 23:46:50 +0000</lastBuildDate>
+    <pubDate>Thu, 3 Aug 2017 10:38:12 +0000</pubDate>
+    <lastBuildDate>Thu, 3 Aug 2017 10:38:12 +0000</lastBuildDate>
diff --git a/content/guides/ppmc-offer.txt b/content/guides/ppmc-offer.txt
new file mode 100644
index 0000000..27b8978
--- /dev/null
+++ b/content/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], and posting 
+a message to
+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
diff --git a/content/guides/ppmc.html b/content/guides/ppmc.html
index 17edc91..7f79420 100644
--- a/content/guides/ppmc.html
+++ b/content/guides/ppmc.html
@@ -408,10 +408,10 @@ the vote result&#8217;s message id of the following form:</p>
 <div class="content">
 <pre class="prettyprint highlight"><code>To: private at
 CC: private at
-Subject: [NOTICE] *Joe Bob* for Podling PPMC
+Subject: [NOTICE] Joe Bob for PODLING PPMC
-Joe Bob has been voted as a new member of the Podling PPMC. the vote thread is at: *link
to the vote thread*</code></pre>
+Joe Bob has been voted as a new member of the *PODLING* PPMC. the vote thread is at: *link
to the vote thread*</code></pre>
 <div class="paragraph">
@@ -422,6 +422,9 @@ process. Failure to do this can result in an embarassing situation
 for people involved.</strong></p>
 <div class="paragraph">
+<p>In the email you send, replace <strong>PODLING</strong> with your podling&#8217;s
actual name, and replace Joe Bob with the prospect&#8217;s actual name.</p>
+<div class="paragraph">
 <p>After 72 hours, Joe Bob
 should be invited to join the PPMC, using a sample message like
 <a href="ppmc-offer.txt">this</a>.</p>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 5373d46..6775138 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -93,7 +93,7 @@
-    	<lastmod>2017-08-02</lastmod>
+    	<lastmod>2017-08-03</lastmod>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message