incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r611570 - in /incubator/public/trunk: site-author/guides/mentor.xml site-publish/guides/mentor.html
Date Sun, 13 Jan 2008 13:16:51 GMT
Author: rdonkin
Date: Sun Jan 13 05:16:49 2008
New Revision: 611570

URL: http://svn.apache.org/viewvc?rev=611570&view=rev
Log:
Mailing lists creation initial content.

Modified:
    incubator/public/trunk/site-author/guides/mentor.xml
    incubator/public/trunk/site-publish/guides/mentor.html

Modified: incubator/public/trunk/site-author/guides/mentor.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/mentor.xml?rev=611570&r1=611569&r2=611570&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/mentor.xml (original)
+++ incubator/public/trunk/site-author/guides/mentor.xml Sun Jan 13 05:16:49 2008
@@ -146,6 +146,9 @@
       sign up then track actions which are
       and use it to organise the startup process by checking off items 
       which are done and assigning individuals to tasks.
+      Much of the information can be filled in from the proposal.
+      Keep the project status page up to date during the bootstrap.
+      This allows anyone to monitor progress
        -->
       </section>
 
@@ -165,13 +168,13 @@
     Following podling creation, it needs to be bootstrapped.
     </p>
     <ol>
-      <li>Initialize project status page [<code>IPMC member</code>]</li>
+      <li><a href='#Initialize+Podling+Status+Page'>Initialize project status
page</a> [<code>IPMC member</code>]</li>
       <li>Start <code>CLA</code> and <code>CCLA</code> submission
[<code>Prospective committers</code>]</li>
       <li>Start <a href='initial-ip-clearance'>IP Clearance</a> 
           [<code>IPMC member</code>]</li>
       <li>Request Required Resources
         <ol>
-        <li>Mailing Lists [<code>Infrastructure Team</code>]</li>
+        <li><a href='#request-mailing-lists'>Mailing Lists</a> [<a href='who-infra'>Infrastructure
Team</a>]</li>
         </ol>
       </li>
     </ol> 
@@ -199,11 +202,70 @@
     
     <section id='request-required-resources'><title>Request Required Resources</title>
       <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>
+      <section id='request-mailing-lists'><title>Request Mailing Lists</title>
+      <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 set up. All mailing lists for a project SHOULD use
+      the project's host as the domain. In particular, the domain for Incubator mailing lists
+      MUST be <code>incubator.apache.org</code>.
+      </p><p>
+      Incubator is the responsible top level project.
       </p><p>
-      Mailing lists. Sort out initial moderators. Link to infra.
+      Mailing lists creation is a task for the <a href='#who-infra'>infrastructure
team</a>. Read 
+      and then follow 
+      <a href='http://www.apache.org/dev/reporting-issues.html#mail-new-lists'>the
instructions</a>.
+      For example, see 
+      <a href='http://issues.apache.org/jira/browse/INFRA-1454'>this JIRA</a>

+      and this email:
+      </p>
+<source>
+From: rdonkin@apache.org
+To: apmail@apache.org
+CC: private@incubator.apache.org
+Subject: Mailing list creation for RAT
+
+The Incubator Project has voted to accept RAT [1]
+
+Please create the following mailing lists in the incubator.apache.org domain:
+
+  rat-private
+  rat-dev
+  rat-commits
+
+Initial moderator for all lists: rdonkin@apache.org
+
+JIRA: INFRA-1454 [2]
+
+Thanks
+
+- robert
+
+[1] http://mail-archives.apache.org/mod_mbox/incubator-general/200711.mbox/%3cf470f68e0711071546k201d2caamb9a7df257bcc96c3@mail.gmail.com%3e
+[2] http://issues.apache.org/jira/browse/INFRA-1454
+</source> 
+      <p>
+      The email MUST be sent from an Apache email address. Typically, this will be sent by

+      a Mentor (though any existing committer may make the request).     
+      </p><p>
+      Remember to update the project status file with progress.
       </p>
+      </section>
     </section>
     
     <section id='who-committers'><title>Prospective Committers</title>
@@ -220,10 +282,14 @@
     </section>
     <section id='who-infra'><title>Infrastructure Team</title>
       <p>
-      This needs to be executed by the Infrastructure team. The relevant instructions
-      need to be followed. Typically, this means created a JIRA.
-      </p>
-    </section>
+      Tasks that cannot safely be delegated to projects are handled by the Apache
+      <a href='http://www.apache.org/dev/infra-volunteer.html'>Infrastructure team</a>.

+      The relevant instructions 
+      <a href='http://www.apache.org/dev/reporting-issues.html#intro'>MUST be followed</a>.

+      <a href='http://issues.apache.org/jira/browse/INFRA'>JIRA</a> is typically
used to
+      manage workflow. This allows progress to be easily tracked. 
+      </p>    
+      </section>
     </section>
     
   </body>

Modified: incubator/public/trunk/site-publish/guides/mentor.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/mentor.html?rev=611570&r1=611569&r2=611570&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/mentor.html (original)
+++ incubator/public/trunk/site-publish/guides/mentor.html Sun Jan 13 05:16:49 2008
@@ -169,6 +169,12 @@
 <li><a href='#request-required-resources'>
 Request Required Resources
  </a>
+ <ul>
+<li><a href='#request-mailing-lists'>
+Request Mailing Lists
+ </a>
+</li>
+</ul>
 </li>
 <li><a href='#who-committers'>
 Prospective Committers
@@ -318,13 +324,13 @@
     Following podling creation, it needs to be bootstrapped.
     </p>
 <ol>
-      <li>Initialize project status page [<code>IPMC member</code>]</li>
+      <li><a href="#Initialize+Podling+Status+Page">Initialize project status
page</a> [<code>IPMC member</code>]</li>
       <li>Start <code>CLA</code> and <code>CCLA</code> submission
[<code>Prospective committers</code>]</li>
       <li>Start <a href="initial-ip-clearance">IP Clearance</a> 
           [<code>IPMC member</code>]</li>
       <li>Request Required Resources
         <ol>
-        <li>Mailing Lists [<code>Infrastructure Team</code>]</li>
+        <li><a href="#request-mailing-lists">Mailing Lists</a> [<a href="who-infra">Infrastructure
Team</a>]</li>
         </ol>
       </li>
     </ol>
@@ -359,13 +365,80 @@
 </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>
+   <a name="request-mailing-lists">Request Mailing Lists</a>
+</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 set up. All mailing lists for a project SHOULD use
+      the project's host as the domain. In particular, the domain for Incubator mailing lists
+      MUST be <code>incubator.apache.org</code>.
+      </p>
+<p>
+      Incubator is the responsible top level project.
+      </p>
+<p>
+      Mailing lists creation is a task for the <a href="#who-infra">infrastructure
team</a>. Read 
+      and then follow 
+      <a href="http://www.apache.org/dev/reporting-issues.html#mail-new-lists">the
instructions</a>.
+      For example, see 
+      <a href="http://issues.apache.org/jira/browse/INFRA-1454">this JIRA</a>

+      and this email:
+      </p>
+<div class="source"><code>
+From: rdonkin@apache.org
+To: apmail@apache.org
+CC: private@incubator.apache.org
+Subject: Mailing list creation for RAT
+
+The Incubator Project has voted to accept RAT [1]
+
+Please create the following mailing lists in the incubator.apache.org domain:
+
+  rat-private
+  rat-dev
+  rat-commits
+
+Initial moderator for all lists: rdonkin@apache.org
+
+JIRA: INFRA-1454 [2]
+
+Thanks
+
+- robert
+
+[1] http://mail-archives.apache.org/mod_mbox/incubator-general/200711.mbox/%3cf470f68e0711071546k201d2caamb9a7df257bcc96c3@mail.gmail.com%3e
+[2] http://issues.apache.org/jira/browse/INFRA-1454
+</code>
+</div>
+<p>
+      The email MUST be sent from an Apache email address. Typically, this will be sent by

+      a Mentor (though any existing committer may make the request).     
+      </p>
 <p>
-      Mailing lists. Sort out initial moderators. Link to infra.
+      Remember to update the project status file with progress.
       </p>
 </div>
+</div>
 <h3>
    <a name="who-committers">Prospective Committers</a>
 </h3>
@@ -388,8 +461,12 @@
 </h3>
 <div class="section-content">
 <p>
-      This needs to be executed by the Infrastructure team. The relevant instructions
-      need to be followed. Typically, this means created a JIRA.
+      Tasks that cannot safely be delegated to projects are handled by the Apache
+      <a href="http://www.apache.org/dev/infra-volunteer.html">Infrastructure team</a>.

+      The relevant instructions 
+      <a href="http://www.apache.org/dev/reporting-issues.html#intro">MUST be followed</a>.

+      <a href="http://issues.apache.org/jira/browse/INFRA">JIRA</a> is typically
used to
+      manage workflow. This allows progress to be easily tracked. 
       </p>
 </div>
 </div>



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


Mime
View raw message