incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1001646 - in /websites/staging/incubator/trunk/content: ./ guides/graduation.html guides/mentor.html guides/pmc.html guides/ppmc.html guides/proposal.html incubation/Incubation_Policy.html report-next-month.html sitemap.html
Date Fri, 25 Nov 2016 21:03:12 GMT
Author: buildbot
Date: Fri Nov 25 21:03:12 2016
New Revision: 1001646

Log:
Staging update by buildbot for incubator

Modified:
    websites/staging/incubator/trunk/content/   (props changed)
    websites/staging/incubator/trunk/content/guides/graduation.html
    websites/staging/incubator/trunk/content/guides/mentor.html
    websites/staging/incubator/trunk/content/guides/pmc.html
    websites/staging/incubator/trunk/content/guides/ppmc.html
    websites/staging/incubator/trunk/content/guides/proposal.html
    websites/staging/incubator/trunk/content/incubation/Incubation_Policy.html
    websites/staging/incubator/trunk/content/report-next-month.html
    websites/staging/incubator/trunk/content/sitemap.html

Propchange: websites/staging/incubator/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 25 21:03:12 2016
@@ -1 +1 @@
-1771186
+1771391

Modified: websites/staging/incubator/trunk/content/guides/graduation.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/graduation.html (original)
+++ websites/staging/incubator/trunk/content/guides/graduation.html Fri Nov 25 21:03:12 2016
@@ -400,17 +400,18 @@ Stay In Touch
                             </li>
                             <li>
 
-                                Demonstrate <a href="#community">community
-                                readiness</a>
+                                Demonstrate <a href="#community">community readiness</a>
 
                             </li>
                             <li>
 
                                 Ensure <a href="../incubation/Roles_and_Responsibilities.html#Mentor">Mentors</a>
and <a href="../incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
-                                have no <a href="#notes-issues">remaining
-                                issues</a>
+                                have no <a href="#notes-issues">remaining issues</a>
 
                             </li>
+                            <li>
+	                            Complete the <a href="http://community.apache.org/apache-way/apache-project-maturity-model.html"
target="_new">Apache Project Maturity Model</a>
+	                        </li>
                         </ul>
                     </li>
                     <li>

Modified: websites/staging/incubator/trunk/content/guides/mentor.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/mentor.html (original)
+++ websites/staging/incubator/trunk/content/guides/mentor.html Fri Nov 25 21:03:12 2016
@@ -146,8 +146,34 @@ Add to Incubation Summary file
 Initialize Podling Status Page
  </a>
 </li>
-<li><a href='#Set+Up+Podling'>
-Set Up Podling
+<li><a href='#request-required-resources'>
+Request Required Resources
+ </a>
+ <ul>
+<li><a href='#request-mailing-lists'>
+Request Mailing Lists
+ </a>
+ <ul>
+<li><a href='#mail-archives'>
+Mail Archives
+ </a>
+</li>
+<li><a href='#mail-admin'>
+Mailing List Administration
+ </a>
+</li>
+<li><a href='#transition-mailing-lists'>
+Mailing List Transition
+ </a>
+</li>
+<li><a href='#request-issue-tracking'>
+Issue Tracking
+ </a>
+</li>
+</ul>
+</li>
+<li><a href='#Set+Up+Podling+Source+Repository'>
+Set Up Podling Source Repository
  </a>
  <ul>
 <li><a href='#Set+Up+GIT+Repository'>
@@ -191,12 +217,6 @@ Establishing Provenance
 <li><a href='#initial-import-code-dump'>
 Initial Code Dump
  </a>
- <ul>
-<li><a href='#svn-history'>
-Importing History
- </a>
-</li>
-</ul>
 </li>
 <li><a href='#crypto-audit'>
 Audit Cryptography
@@ -205,12 +225,6 @@ Audit Cryptography
 <li><a href='#initial-clean-up'>
 Initial Clean Up
  </a>
- <ul>
-<li><a href='#clean-up-best-practice'>
-Clean Up Best Practice
- </a>
-</li>
-</ul>
 </li>
 <li><a href='#repackaging'>
 On Repackaging
@@ -219,38 +233,6 @@ On Repackaging
 <li><a href='#documents-clean-up'>
 Update Documents
  </a>
- <ul>
-<li><a href='#build-clean-up'>
-Update Build
- </a>
-</li>
-</ul>
-</li>
-</ul>
-</li>
-<li><a href='#request-required-resources'>
-Request Required Resources
- </a>
- <ul>
-<li><a href='#request-mailing-lists'>
-Request Mailing Lists
- </a>
- <ul>
-<li><a href='#mail-archives'>
-Mail Archives
- </a>
-</li>
-<li><a href='#mail-admin'>
-Mailing List Administration
- </a>
-</li>
-<li><a href='#transition-mailing-lists'>
-Mailing List Transition
- </a>
-</li>
-<li><a href='#request-issue-tracking'>
-Issue Tracking
- </a>
 </li>
 </ul>
 </li>
@@ -304,7 +286,7 @@ Incubator Access Authorization
         <h2 id='Overview'><img src="../images/redarrow.gif" />Overview</h2>
 <div class="section-content">
 <p>
-          After the Podling has been accepted by the Incubator PMC, the mentor 
+          After the Podling has been accepted by the Incubator PMC, one of the mentors 
           <a href="../incubation/Incubation_Policy.html#Setting+Up+a+New+Podling">sets
up</a>
           the Podling; <em>i.e.</em> adds the podling metadata, creates the initial
Podling status page, and 
           either creates or requests that 
@@ -373,131 +355,259 @@ Incubator Access Authorization
       committers subscribe then these may be used for discussion.
       </p>
 </div>
-        <h2 id='Set+Up+Podling'><img src="../images/redarrow.gif" />Set Up Podling</h2>
+        <h2 id='request-required-resources'><img src="../images/redarrow.gif" />Request
Required Resources</h2>
 <div class="section-content">
 <p>
-      The most important responsibility for mentors is to set up the
-      podling source repository. Podlings can choose between svn and
-      git for source control.
-      </p>
-<h3 id='Set+Up+GIT+Repository'>Set up GIT Repository</h3>
+	      The proposal should include a list of required resources. All of these will 
+	      require active set up. Some are created by infrastructure after an appropriate
+	      request, others can be set up by any IPMC members (typically mentors).
+	      </p>
+<p>
+	      Mailing lists should be created first. Other resources typically
+	      post information to these lists.
+	      </p>
+<h3 id='request-mailing-lists'>Request Mailing Lists</h3>
+<div class="section-content">
+<p>
+	      Apache mailing lists require volunteer moderators. New moderators can be 
+	      <a href="http://www.apache.org/dev/committers.html#mailing-list-moderators">changed
later</a> 
+	      but at least one volunteer is required before the mailing lists can be set up. 
+	      Moderation is a reasonably 
+	      <a href="http://www.apache.org/dev/committers.html#mail-moderate">easy task</a>
+	      though moderators may want to set up 
+	      <a href="http://spamassassin.apache.org/">spam filtering</a>.
+	      Having at least three moderators is recommended to spread the load.
+	      </p>
+<p>
+	      The proposal should contain the rest of the information that needs to be collected
+	      before the mailing lists can be requested. Incubator is the responsible top level
project.
+	      So the domain <code>MUST</code> be <code>incubator.apache.org</code>.
+	      For example:
+	      </p>
+<ul>
+	      <li>dev@${podling}.incubator.apache.org</li>
+	      <li>commits@${podling}.incubator.apache.org</li>
+	      <li>private@${podling}.incubator.apache.org</li>
+	      </ul>
+<p>
+	        For initial community building it is usually appropriate to only have
+	        a "dev" list, to keep the discussions focussed. Later add a "user" list
+	        if needed.
+	      </p>
+<div class="note">
+<note>
+	Commits under <code>http://svn.apache.org/repos/asf/incubator/<em>${podling}</em></code>
+	will be emailed to <code>commits@${podling}.incubator.apache.org</code>.
+	Any deviation will 
+	require special configuration in the <code>asf-mailer.conf</code> file by the
IPMC.
+	      </note>
+</div>
+<p>
+	      Mailing lists creation is a task for the <a href="#who-infra">infrastructure
team</a>. The
+	      infrastructure team offers a tool that simplifies the creation of mailing lists. 
You can access the
+	      <a href="https://infra.apache.org/officers/mlreq/incubator" target="_new">Incubator
Mailing List Request Form</a>
+	      to request a list.  A notification will be sent to private@incubator when the lists
have been created.
+	      </p>
+<p>
+	      Remember to update the project status file with mailing list details. Prospective
committers 
+	      and mentors will need to subscribe. Email them once the status file has been updated.
Inform
+	      any existing mailing lists or forums previously used by the project.
+	      </p>
+<p>
+	      Once the <code>commits</code> list is created, the project MUST review
+	      the <code>/incubator/${podling}</code> tree, since any commits made prior
+	      to the list's creation will have generated no email trail.
+	      </p>
+<h4 id='mail-archives'>Mail Archives</h4>
 <div class="section-content">
 <p>
-       Setting up git for a podling is simple. You open a JIRA to 
-       INFRA and request it.  You can either ask for a bare
-       repository or for a repository imported from some
-       publically-accessible existing repository; tell infra what you
-       need.
-       </p>
-<p>
-       The Foundation's policy 
-       is to grant access to git repositories broadly to the incubator group,
-       not narrowly podling-by-podling. So, once the repository
-       exists, incubator group members gain access without further work.  Once
-       the podling graduates, a dedicated ldap group will be created to manage
-       access and only those members will be given access.
-       </p>
-</div>
-<h3 id='Set+Up+SVN+Repository'>Set Up SVN Repository</h3>
-<div class="section-content">
-<p>
-      If the podling chooses svn, you must create the 
-      repository and give read/write access to the repository
-      to all the committers for the podling. This involves requesting
-      new committer accounts and granting access to mentors and existing
-      Apache committers.
-      </p>
+	Archives at <a href="http://mail-archives.apache.org">http://mail-archives.apache.org</a>
for the public
+	mailing lists will be setup as part of the mailing list creation process. No action is
+	required by Mentors. The archives will be <a href="http://mail-archives.apache.org/mod_mbox/">visible</a>

+	as soon as posts have been made (and moderated) to these lists.
+	        </p>
+<p>
+		    You can also leverage <a href="https://lists.apache.org" target="_new">lists.apache.org</a>
for 
+		    mailing list archives.  There is a login link in the top right corner, which allows
you to respond to
+		    threads from within the web application.
+		    </p>
+<p>
+	Many projects are independently archived externally (for example, at
+	<a href="http://www.mail-archive.com/">The Mail Archive</a> and 
+	<a href="http://marc.info/?q=about">MARC</a>)
+	Independent archives help to
+	increase project visibility as well as preserving a independent historic record.
+	These subscriptions are not automatically created. If desired, subscribe manually.
+	        </p>
+<p>
+	Subscriptions to news-to-mailing-list bridges (for example, <a href="http://www.nabble.com">Nabble</a>)
+	must also be created manually. Subscribing helps accessibility and visibility but Nabble
news
+	users may not be aware that they are posting to a mailing list.
+	        </p>
+</div>
+<h4 id='mail-admin'>Mailing List Administration</h4>
+<div class="section-content">
+<p>
+	Apache uses <a href="http://www.ezmlm.org/">ezmlm</a>. See the 
+	<a href="http://www.ezmlm.org/man/ezmlmman.html">manual</a> and 
+	committer <a href="http://www.apache.org/dev/committers.html#mail">mail FAQ</a>
+	for more details.
+	        </p>
+</div>
+<h4 id='transition-mailing-lists'>Mailing List Transition</h4>
+<div class="section-content">
+<p>
+	Independent mailing lists and groups are perfectly acceptable but development should
+	happen on the official mailing lists at Apache. If a project has existing mailing lists,
+	forums or groups the community needs to consider their future and plan for the transition
+	to the official Apache mailing lists.
+	        </p>
+<p>
+	It may be useful to move development first to the official lists followed gradually 
+	by the user resources.
+	        </p>
+<p>
+	        Note that subscribers of external mailing lists will not be automatically subscribed
+	        to the new Incubator project mailing lists. Instead, a note should be posted to
the
+	        old external mailing list asking them to subscribe to the new list. If possible,
add
+	        a footer to the old mailing list with some instructions.
+	        </p>
+</div>
+<h4 id='request-issue-tracking'>Issue Tracking</h4>
+<div class="section-content">
+<p>
+		If any Mentor has project-creation karma (in the issue tracking system to be used) 
+		then they should execute.
+		If no Mentor has the required karma then file an INFRA issue using the 'new jira project'

+		type (not bug or request)
+	        </p>
+<p>
+	Remember to post an email announcing that the issue tracker is available.
+	        </p>
+</div>
+</div>
+<h3 id='Set+Up+Podling+Source+Repository'>Set Up Podling Source Repository</h3>
+<div class="section-content">
+<p>
+		      The most important responsibility for mentors is to set up the
+		      podling source repository. Podlings can choose between svn and
+		      git for source control.
+		      </p>
+<h4 id='Set+Up+GIT+Repository'>Set up GIT Repository</h4>
+<div class="section-content">
+<p>
+		       Requests for new git repos are done via <a href="https://reporeq.apache.org/"
target="_new">reporeq.apache.org</a>.
+		       This service will initialize a new repository, setup github mirrors and enable integrations
for that repository.
+		       </p>
+<p>
+		       The Foundation's policy 
+		       is to grant access to git repositories broadly to the incubator group,
+		       not narrowly podling-by-podling. So, once the repository
+		       exists, incubator group members gain access without further work.  Once
+		       the podling graduates, a dedicated ldap group will be created to manage
+		       access and only those members will be given access.
+		       </p>
+</div>
+<h4 id='Set+Up+SVN+Repository'>Set Up SVN Repository</h4>
+<div class="section-content">
+<p>
+		      If the podling chooses svn, you must create the 
+		      repository and give read/write access to the repository
+		      to all the committers for the podling. This involves requesting
+		      new committer accounts and granting access to mentors and existing
+		      Apache committers.
+		      </p>
 <p>Setting up a podling subversion repository has two steps: Creating the SVN space
-        and configuring the authorization (in both svn and git).
-      </p>
+		        and configuring the authorization (in both svn and git).
+		      </p>
 <p>
-      Create the workspace in svn. This requires commit access to the
-      incubator svn repository. Podlings are given their own subdirectory
-      of the incubator svn repository. To create the podling subdirectory,
-      the mentor executes the svn command to create a remote directory:
-      <code>
-      svn mkdir https://svn.apache.org/repos/asf/incubator/{podling}
-      </code>
-      </p>
+		      Create the workspace in svn. This requires commit access to the
+		      incubator svn repository. Podlings are given their own subdirectory
+		      of the incubator svn repository. To create the podling subdirectory,
+		      the mentor executes the svn command to create a remote directory:
+		      <code>
+		      svn mkdir https://svn.apache.org/repos/asf/incubator/{podling}
+		      </code>
+		      </p>
 <p>Create the workspace authorization in asf-authorization-template.
-      This requires commit access to the file 
-      <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template</code>
-      as well as commit access to the git repo <code>infrastructure-puppet</code>
to update the file 
-      <code>modules/subversion_server/files/authorization/asf-authorization-template</code>.
Please follow the procedures in the <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo">infrastructure
puppet workflow</a> document.
-      </p>
+		      This requires commit access to the file 
+		      <code>https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template</code>
+		      as well as commit access to the git repo <code>infrastructure-puppet</code>
to update the file 
+		      <code>modules/subversion_server/files/authorization/asf-authorization-template</code>.
Please follow the procedures in the <a href="https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo">infrastructure
puppet workflow</a> document.
+		      </p>
 <p>
-      Edit the file to add the podling repository in alphabetical order, e.g.
-      </p>
+		      Edit the file to add the podling repository in alphabetical order, e.g.
+		      </p>
 <div class="source"><code>{podling}={mentor1},{mentor2}</code>
 </div>
 <p>
-      In the section listing all the projects (again in alphabetical order)
-      add the podling directory and permissions, to enable the podling for its
-      eventual website:
-      </p>
+		      In the section listing all the projects (again in alphabetical order)
+		      add the podling directory and permissions, to enable the podling for its
+		      eventual website:
+		      </p>
 <div class="source"><code>[/incubator/{podling}]
-@{podling} = rw
-...</code>
+		@{podling} = rw
+		...</code>
 </div>
 <p>
-      Enable the podling for the Incubator website:
-      </p>
+		      Enable the podling for the Incubator website:
+		      </p>
 <div class="source"><code>[/incubator/public]
-...
-@{podling} = rw
-...</code>
+		...
+		@{podling} = rw
+		...</code>
 </div>
 <p>
-This is a convenient time to add <a href="#Authorize+Committers">authorization</a>
for committers 
-who have accounts.
-      </p>
+		This is a convenient time to add <a href="#Authorize+Committers">authorization</a>
for committers 
+		who have accounts.
+		      </p>
 <p>
-<a href="#who-auth-karma">Authorization</a> karma is restricted. If no Mentor
-has this karma then post an email to IPMC private list requesting that this 
-is actioned.
-      </p>
+		<a href="#who-auth-karma">Authorization</a> karma is restricted. If no Mentor
+		has this karma then post an email to IPMC private list requesting that this 
+		is actioned.
+		      </p>
 </div>
-<h3 id='Authorize+Committers'>Authorize Committers</h3>
+<h4 id='Authorize+Committers'>Authorize Committers</h4>
 <div class="section-content">
 <p>The process to add committers to the podling depends on whether 
-         the new committer is already an Apache committer and whether
-         the new committer is in the list of original committers: 
-      </p>
+		         the new committer is already an Apache committer and whether
+		         the new committer is in the list of original committers: 
+		      </p>
 <ul>
-      <li>The committer is in the list of original committers in the 
-          podling proposal to the incubator and is not already an Apache
-          committer:
-        <ul>
-        <li>
-          Ask developers to send their ICLA to secretary@apache.org according to 
-          <a href="http://apache.org/licenses/#submitting">standard procedure.</a>
-          Note that ICLA forms must be signed, either by hand or by digital signature.
-        </li>
-        <li>
-          Developers should choose an Apache id that is not already listed 
-          <a href="http://people.apache.org/committer-index.html">here.</a>
-        </li>
-        <li>
-          Developers should enter their preferred Apache id on the ICLA 
-          and enter the podling name in the "notify" field of the ICLA.
-        </li>
-        </ul>
-      </li>
-      <li> The committer is in the list of original committers in the 
-         podling proposal to the incubator and is already an Apache committer, only
-         <a href="#who-auth-karma">incubator authorization</a> is required. 
-      </li>
-      <li>The committer was voted by the PPMC and approved by the incubator
-          PMC:
-      </li>
-      <p>
-        Perform one of the above procedures depending on whether the 
-        committer is already an Apache committer on another project.
-      </p>
-      </ul>
+		      <li>The committer is in the list of original committers in the 
+		          podling proposal to the incubator and is not already an Apache
+		          committer:
+		        <ul>
+		        <li>
+		          Ask developers to send their ICLA to secretary@apache.org according to 
+		          <a href="http://apache.org/licenses/#submitting">standard procedure.</a>
+		          Note that ICLA forms must be signed, either by hand or by digital signature.
+		        </li>
+		        <li>
+		          Developers should choose an Apache id that is not already listed 
+		          <a href="http://people.apache.org/committer-index.html">here.</a>
+		        </li>
+		        <li>
+		          Developers should enter their preferred Apache id on the ICLA 
+		          and enter the podling name in the "notify" field of the ICLA.
+		        </li>
+		        </ul>
+		      </li>
+		      <li> The committer is in the list of original committers in the 
+		         podling proposal to the incubator and is already an Apache committer, only
+		         <a href="#who-auth-karma">incubator authorization</a> is required.

+		      </li>
+		      <li>The committer was voted by the PPMC and approved by the incubator
+		          PMC:
+		      </li>
+		      <p>
+		        Perform one of the above procedures depending on whether the 
+		        committer is already an Apache committer on another project.
+		      </p>
+		      </ul>
 </div>
 </div>
-        <h2 id='bootstrap'><img src="../images/redarrow.gif" />[DRAFT] Podling
Bootstrap</h2>
+<h3 id='bootstrap'>[DRAFT] Podling Bootstrap</h3>
 <div class="section-content">
 <p>
     <strong>NOTE</strong> This section is a DRAFT under development.
@@ -536,7 +646,7 @@ is actioned.
       </li>
       
     </ol>
-<h3 id='mentors-ipmc'>Mentors MUST be on the IPMC</h3>
+<h4 id='mentors-ipmc'>Mentors MUST be on the IPMC</h4>
 <div class="section-content">
 <p>
 Mentors <a href="../incubation/Incubation_Policy.html#Mentor">MUST</a> be on
the IPMC.
@@ -549,7 +659,7 @@ This process may take a few days.
       </note>
 </div>
 </div>
-<h3 id='submit-cla'>CLA and CCLA Submission</h3>
+<h4 id='submit-cla'>CLA and CCLA Submission</h4>
 <div class="section-content">
 <p>
       Prospective committers need to submit a
@@ -559,9 +669,9 @@ This process may take a few days.
       these as soon as the podling is accepted.
       </p>
 </div>
-<h3 id='initial-ip-clearance'>IP Clearance</h3>
+<h4 id='initial-ip-clearance'>IP Clearance</h4>
 <div class="section-content">
-<h4 id='initial-up-clearance-general'>Background</h4>
+<h5 id='initial-up-clearance-general'>Background</h5> 
 <div class="section-content">
 <p>
       Existing codebases need to be imported through the standard IP clearance
@@ -580,7 +690,7 @@ This process may take a few days.
       <a href="#poding-ip-clearance">process for podlings</a>.
       </p>
 </div>
-<h4 id='initial-provenance'>Establishing Provenance</h4>
+<h5 id='initial-provenance'>Establishing Provenance</h5> 
 <div class="section-content">
 <p>
         Paperwork needs to be submitted to Apache that grants a legal license on the code

@@ -621,7 +731,7 @@ This process may take a few days.
         general list.
         </p>
 </div>
-<h4 id='initial-import-code-dump'>Initial Code Dump</h4>
+<h5 id='initial-import-code-dump'>Initial Code Dump</h5> 
 <div class="section-content">
 <p>
         For corporate contributions, the SGA or CCLA MUST be completed, submitted
@@ -659,7 +769,7 @@ please ask the infrastructure team polit
           </p>
 </div>
 </div>
-<h4 id='crypto-audit'>Audit Cryptography</h4>
+<h5 id='crypto-audit'>Audit Cryptography</h5> 
 <div class="section-content">
 <p>
         Before the code base is committed into an Apache repository, the contribution
@@ -668,7 +778,7 @@ please ask the infrastructure team polit
         <a href="http://www.apache.org/dev/crypto.html">this guide</a>.
         </p>
 </div>
-<h4 id='initial-clean-up'>Initial Clean Up</h4>
+<h5 id='initial-clean-up'>Initial Clean Up</h5> 
 <div class="section-content">
 <p>
           Once a JIRA has been created, the source should be cleaned up.
@@ -773,7 +883,7 @@ please ask the infrastructure team polit
           </p>
 </div>
 </div>
-<h4 id='repackaging'>On Repackaging</h4>
+<h5 id='repackaging'>On Repackaging</h5> 
 <div class="section-content">
 <p>
         It is recommended - but not mandated - that source is repackaged
@@ -786,7 +896,7 @@ please ask the infrastructure team polit
         carefully how they will approach this transition.
         </p>
 </div>
-<h4 id='documents-clean-up'>Update Documents</h4>
+<h5 id='documents-clean-up'>Update Documents</h5> 
 <div class="section-content">
 <p>
         Check the documentation for references to the old home of the project and update
them 
@@ -831,133 +941,6 @@ please ask the infrastructure team polit
 </div>
 </div>
 </div>
-<h3 id='request-required-resources'>Request Required Resources</h3>
-<div class="section-content">
-<p>
-      The proposal should include a list of required resources. All of these will 
-      require active set up. Some are created by infrastructure after an appropriate
-      request, others can be set up by any IPMC members (typically mentors).
-      </p>
-<p>
-      Mailing lists should be created first. Other resources typically
-      post information to these lists.
-      </p>
-<h4 id='request-mailing-lists'>Request Mailing Lists</h4>
-<div class="section-content">
-<p>
-      Apache mailing lists require volunteer moderators. New moderators can be 
-      <a href="http://www.apache.org/dev/committers.html#mailing-list-moderators">changed
later</a> 
-      but at least one volunteer is required before the mailing lists can be set up. 
-      Moderation is a reasonably 
-      <a href="http://www.apache.org/dev/committers.html#mail-moderate">easy task</a>
-      though moderators may want to set up 
-      <a href="http://spamassassin.apache.org/">spam filtering</a>.
-      Having at least three moderators is recommended to spread the load.
-      </p>
-<p>
-      The proposal should contain the rest of the information that needs to be collected
-      before the mailing lists can be requested. Incubator is the responsible top level project.
-      So the domain <code>MUST</code> be <code>incubator.apache.org</code>.
-      For example:
-      </p>
-<ul>
-      <li>dev@${podling}.incubator.apache.org</li>
-      <li>commits@${podling}.incubator.apache.org</li>
-      <li>private@${podling}.incubator.apache.org</li>
-      </ul>
-<p>
-        For initial community building it is usually appropriate to only have
-        a "dev" list, to keep the discussions focussed. Later add a "user" list
-        if needed.
-      </p>
-<div class="note">
-<note>
-Commits under <code>http://svn.apache.org/repos/asf/incubator/<em>${podling}</em></code>
-will be emailed to <code>commits@${podling}.incubator.apache.org</code>.
-Any deviation will 
-require special configuration in the <code>asf-mailer.conf</code> file by the
IPMC.
-      </note>
-</div>
-<p>
-      Mailing lists creation is a task for the <a href="#who-infra">infrastructure
team</a>. The
-      infrastructure team offers a tool that simplifies the creation of mailing lists - please
 
-      visit the <a href="https://infra.apache.org/">infrastructure site</a> for
the latest link.
-      Note that there is an incubator-specific link at the bottom of the initial form. A
notification
-      will be sent to private@incubator when the lists have been created.
-      </p>
-<p>
-      Remember to update the project status file with mailing list details. Prospective committers

-      and mentors will need to subscribe. Email them once the status file has been updated.
Inform
-      any existing mailing lists or forums previously used by the project.
-      </p>
-<p>
-      Once the <code>commits</code> list is created, the project MUST review
-      the <code>/incubator/${podling}</code> tree, since any commits made prior
-      to the list's creation will have generated no email trail.
-      </p>
-<h5 id='mail-archives'>Mail Archives</h5> 
-<div class="section-content">
-<p>
-Archives at <a href="http://mail-archives.apache.org">http://mail-archives.apache.org</a>
for the public
-mailing lists will be setup as part of the mailing list creation process. No action is
-required by Mentors. The archives will be <a href="http://mail-archives.apache.org/mod_mbox/">visible</a>

-as soon as posts have been made (and moderated) to these lists.
-        </p>
-<p>
-Many projects are independently archived externally (for example, at
-<a href="http://www.mail-archive.com/">The Mail Archive</a> and 
-<a href="http://marc.info/?q=about">MARC</a>)
-Independent archives help to
-increase project visibility as well as preserving a independent historic record.
-These subscriptions are not automatically created. If desired, subscribe manually.
-        </p>
-<p>
-Subscriptions to news-to-mailing-list bridges (for example, <a href="http://www.nabble.com">Nabble</a>)
-must also be created manually. Subscribing helps accessibility and visibility but Nabble
news
-users may not be aware that they are posting to a mailing list.
-        </p>
-</div>
-<h5 id='mail-admin'>Mailing List Administration</h5> 
-<div class="section-content">
-<p>
-Apache uses <a href="http://www.ezmlm.org/">ezmlm</a>. See the 
-<a href="http://www.ezmlm.org/man/ezmlmman.html">manual</a> and 
-committer <a href="http://www.apache.org/dev/committers.html#mail">mail FAQ</a>
-for more details.
-        </p>
-</div>
-<h5 id='transition-mailing-lists'>Mailing List Transition</h5> 
-<div class="section-content">
-<p>
-Independent mailing lists and groups are perfectly acceptable but development should
-happen on the official mailing lists at Apache. If a project has existing mailing lists,
-forums or groups the community needs to consider their future and plan for the transition
-to the official Apache mailing lists.
-        </p>
-<p>
-It may be useful to move development first to the official lists followed gradually 
-by the user resources.
-        </p>
-<p>
-        Note that subscribers of external mailing lists will not be automatically subscribed
-        to the new Incubator project mailing lists. Instead, a note should be posted to the
-        old external mailing list asking them to subscribe to the new list. If possible,
add
-        a footer to the old mailing list with some instructions.
-        </p>
-</div>
-<h5 id='request-issue-tracking'>Issue Tracking</h5> 
-<div class="section-content">
-<p>
-	If any Mentor has project-creation karma (in the issue tracking system to be used) 
-	then they should execute.
-	If no Mentor has the required karma then file an INFRA issue using the 'new jira project'

-	type (not bug or request)
-        </p>
-<p>
-Remember to post an email announcing that the issue tracker is available.
-        </p>
-</div>
-</div>
 <h4 id='orientation'>Orientating New Committers: Understanding Apache</h4>
 <div class="section-content">
 <p>

Modified: websites/staging/incubator/trunk/content/guides/pmc.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/pmc.html (original)
+++ websites/staging/incubator/trunk/content/guides/pmc.html Fri Nov 25 21:03:12 2016
@@ -24,7 +24,7 @@
   <link rel="stylesheet" href="../style/bootstrap-1-3-0-min.css" type="text/css" />
   <link rel="stylesheet" href="../style/style.css" type="text/css" />
     <link rel="alternate" title="general@incubator.apache.org Archives" type="application/atom+xml"
href="http://mail-archives.apache.org/mod_mbox/incubator-general/?format=atom" />
-    <title>PMC - Apache Incubator</title>
+    <title>Incubator PMC Responsibilities - Apache Incubator</title>
   
  </head>
  <body>

Modified: websites/staging/incubator/trunk/content/guides/ppmc.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/ppmc.html (original)
+++ websites/staging/incubator/trunk/content/guides/ppmc.html Fri Nov 25 21:03:12 2016
@@ -274,11 +274,8 @@
       with a subject line of [DISCUSS] Joe Bob PPMC membership. If there
       is consensus that the proposed member is suitable, then there should
       be a formal vote in the PPMC private alias, with the subject line of
-      [VOTE] Joe Bob PPMC membership. The [VOTE] message should be forwarded
-      to the IPMC (<a href="mailto:private@incubator.apache.org">
-      private@incubator.apache.org</a>) to notify them that the
-      vote is underway. Do not CC or BCC the IPMC on this thread.  Instead,
-      forward the initial VOTE email.</p>
+      [VOTE] Joe Bob PPMC membership.
+      </p>
 <p>If the vote is successful, the proposer 
       should send a message to the PPMC private alias, with
       the subject line of [VOTE][RESULT] Joe Bob PPMC membership. The
@@ -340,6 +337,18 @@
 		they may want to drop a mail on the general incubator mailing list to try
 		to recruit a new mentor.</p>
 </div>
+        <h2 id='PPMC+binding+votes'><img src="../images/redarrow.gif" />PPMC
and Binding Votes</h2>
+<div class="section-content">
+<p>
+	   The only time when a PPMC member's vote is binding is for the addition of
+	   new PPMC members and committers.  Release votes are only binding to IPMC
+	   members.
+	  </p>
+<p>
+		The binding status of a person's vote is not related to the mailing list
+		that the vote is occurring on.
+	  </p>
+</div>
        </div>
    </div>
   

Modified: websites/staging/incubator/trunk/content/guides/proposal.html
==============================================================================
--- websites/staging/incubator/trunk/content/guides/proposal.html (original)
+++ websites/staging/incubator/trunk/content/guides/proposal.html Fri Nov 25 21:03:12 2016
@@ -423,7 +423,7 @@ Use the template as a guide but do not f
 by it. Adopt what works and change what doesn't. That's fine - in fact, it's expected. 
        </p>
 <p>
-Be sure to add your pproposal to <a href="http://wiki.apache.org/incubator/ProjectProposals">this
list</a>.
+Be sure to add your proposal to <a href="http://wiki.apache.org/incubator/ProjectProposals">this
list</a>.
        </p>
 </div>
 <h3 id='name'>Project Name</h3>
@@ -1432,7 +1432,7 @@ a person already associated with Apache
 <a href="#template-mentors">Mentor</a>.
 				</p>
 				<p>
-A Champion should be found before the proposal is formally submitted. 
+A Champion should be found while the proposal is still being formulated.  Their role is to
help formulate the proposal and work with you to resolve comments and questions put forth
by the IPMC while reviewing the proposal.
                 </p>
                 </note>
 </div>

Modified: websites/staging/incubator/trunk/content/incubation/Incubation_Policy.html
==============================================================================
--- websites/staging/incubator/trunk/content/incubation/Incubation_Policy.html (original)
+++ websites/staging/incubator/trunk/content/incubation/Incubation_Policy.html Fri Nov 25
21:03:12 2016
@@ -875,12 +875,10 @@ This role and its responsibilities are d
 </h3>
 <div class="section-content">
 <p>A Podling has one or more Mentors, one of which MUST be an Apache Member. 
-Mentors are chosen by the Sponsor to actively monitor the
-podling, guide the podling in 
+Mentors are responsible for actively monitoring the podling, guide the podling in 
 <a href="http://apache.org/foundation/how-it-works.html">the Apache Way</a>,
-and report its status 
-to the Sponsor and the Incubator PMC. All Mentors must be members of the
-Incubator PMC. A Mentor has
+and report its status to the Sponsor and the Incubator PMC. All Mentors must 
+be members of the Incubator PMC. A Mentor has
 <a href="Roles_and_Responsibilities.html#Mentor">responsibilities</a>
 toward the Incubator PMC, the Sponsor, and the community of the assigned
 Podling.

Modified: websites/staging/incubator/trunk/content/report-next-month.html
==============================================================================
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Fri Nov 25 21:03:12 2016
@@ -67,7 +67,7 @@
 <h1>
 <a href="http://incubator.apache.org">Apache Incubator</a> Podlings needing to
prepare report for December</h1>
 <div style="text-align:right;">
-<i>Generated on 2016-11-24T16:42:03Z</i>
+<i>Generated on 2016-11-25T21:02:53Z</i>
 </div>
 <nav>
 <ul>

Modified: websites/staging/incubator/trunk/content/sitemap.html
==============================================================================
--- websites/staging/incubator/trunk/content/sitemap.html (original)
+++ websites/staging/incubator/trunk/content/sitemap.html Fri Nov 25 21:03:12 2016
@@ -624,7 +624,27 @@ Site map of <a href="http://incubator.ap
 <a href="guides/mentor.html#Initialize+Podling+Status+Page">Initialize Podling Status
Page</a>
 </li>
 <li>
-<a href="guides/mentor.html#Set+Up+Podling">Set Up Podling</a>
+<a href="guides/mentor.html#request-required-resources">Request Required Resources</a>
+<ul>
+<li>
+<a href="guides/mentor.html#request-mailing-lists">Request Mailing Lists</a>
+<ul>
+<li>
+<a href="guides/mentor.html#mail-archives">Mail Archives</a>
+</li>
+<li>
+<a href="guides/mentor.html#mail-admin">Mailing List Administration</a>
+</li>
+<li>
+<a href="guides/mentor.html#transition-mailing-lists">Mailing List Transition</a>
+</li>
+<li>
+<a href="guides/mentor.html#request-issue-tracking">Issue Tracking</a>
+</li>
+</ul>
+</li>
+<li>
+<a href="guides/mentor.html#Set+Up+Podling+Source+Repository">Set Up Podling Source
Repository</a>
 <ul>
 <li>
 <a href="guides/mentor.html#Set+Up+GIT+Repository">Set up GIT Repository</a>
@@ -688,26 +708,6 @@ Site map of <a href="http://incubator.ap
 </ul>
 </li>
 <li>
-<a href="guides/mentor.html#request-required-resources">Request Required Resources</a>
-<ul>
-<li>
-<a href="guides/mentor.html#request-mailing-lists">Request Mailing Lists</a>
-<ul>
-<li>
-<a href="guides/mentor.html#mail-archives">Mail Archives</a>
-</li>
-<li>
-<a href="guides/mentor.html#mail-admin">Mailing List Administration</a>
-</li>
-<li>
-<a href="guides/mentor.html#transition-mailing-lists">Mailing List Transition</a>
-</li>
-<li>
-<a href="guides/mentor.html#request-issue-tracking">Issue Tracking</a>
-</li>
-</ul>
-</li>
-<li>
 <a href="guides/mentor.html#orientation">Orientating New Committers: Understanding
Apache</a>
 </li>
 <li>
@@ -840,7 +840,7 @@ Site map of <a href="http://incubator.ap
 </li>
 </ul>
 </li><li>
-<a href="guides/pmc.html">PMC</a>
+<a href="guides/pmc.html">Incubator PMC Responsibilities</a>
 <ul>
 <li>
 <a href="guides/pmc.html#Incubator+PMC+Guides">Incubator PMC Guides</a>
@@ -878,6 +878,9 @@ Site map of <a href="http://incubator.ap
 <li>
 <a href="guides/ppmc.html#Adding+new+mentors">Adding new mentors</a>
 </li>
+<li>
+<a href="guides/ppmc.html#PPMC+binding+votes">PPMC and Binding Votes</a>
+</li>
 </ul>
 </li><li>
 <a href="guides/proposal.html">A Guide To Proposal Creation</a>




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


Mime
View raw message