incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r547905 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Sat, 16 Jun 2007 11:19:26 GMT
Author: rdonkin
Date: Sat Jun 16 04:19:25 2007
New Revision: 547905

URL: http://svn.apache.org/viewvc?view=rev&rev=547905
Log:
Added section about oversight.

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

Modified: incubator/public/trunk/site-author/guides/graduation.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/graduation.xml?view=diff&rev=547905&r1=547904&r2=547905
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Sat Jun 16 04:19:25 2007
@@ -1136,26 +1136,74 @@
               </ul>
             </p>
           </section>
-          <section id='security'>
-            <title>Security</title>
-            <p>
-    
-              Each project needs to be able to manage security. By their
-                      nature, these issues need to be dealt with in private. These
-                      issues may either be dealt with on a separate list or by the
-                      private list. Which list is suitable for security issues
-                      should be noted.
-    
-            </p>
-            <p>
-    
-              Volunteers need to be found from the <a
-                      href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>
-                      to work with the Apache security team and act as first
-                      contacts on security matters.
-    
-            </p>
-          </section>
+              <section id='new-responsibilities'>
+                <title>New Responsibilities</title>
+                <section id='oversight'>
+                  <title>Oversight</title>
+                  <p>
+                    During the stay in the Incubator, the
+                    <a
+                      href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>
+                      Incubator PMC (IPMC)
+                    </a>
+                    was responsible to the
+                    <a
+                      href='/incubation/Roles_and_Responsibilities.html#board'>
+                      Board
+                    </a>
+                    for oversight. A graduated project must now take
+                    responsibility for it's own oversight.
+                  </p>
+                  <p>
+                    A project needs to ensure that it's code base is
+                    clean from an IP perspective. New committers need to
+                    recruited, educated and mentored. Quality releases
+                    need to be cut. Community spirit needs to be maintained
+                    and conflicts resolved positively. Board reports need
+                    to be accurate and prompt.
+                  </p>
+                  <p>
+                    Help is still available but the
+                    appropriate bodies (infrastructure, community, legal
+                    and so on) should now be approached directly.
+                  </p>
+                </section>
+                <section id='security'>
+                  <title>Security</title>
+                  <p>
+
+                    Each project needs to be able to manage security issues
+                    discovered in their code. By their nature, these issues 
+                    need to be dealt with in private. These issues may either 
+                    be dealt with on a separate security list or on the 
+                    private list. Which list is suitable for security issues 
+                    should be noted.
+
+                  </p>
+                  <p>
+
+                    Volunteers need to be found from the
+                    <a
+                      href='http://www.apache.org/foundation/how-it-works.html#structure'>
+                      PMC
+                    </a>
+                    to work with the Apache security team and act as
+                    first contacts on security matters. The new project 
+                    should make contact with the team soon after graduation
+                    and not wait for the first issue to be raised.
+
+                  </p>
+                  <p>
+                  
+                    Projects should adopt a positive attitude towards
+                    security issues. It is easy to gain a poor reputation
+                    by mishandling of these issues. There are many people
+                    at Apache with considerable experience in this area
+                    so ask first.
+                  
+                  </p>
+                </section>
+              </section>
 			</section>
 		</section>
 	</body>

Modified: incubator/public/trunk/site-publish/guides/graduation.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/graduation.html?view=diff&rev=547905&r1=547904&r2=547905
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Sat Jun 16 04:19:25 2007
@@ -248,6 +248,14 @@
 Removing the Podling from Incubation
  </a>
 </li>
+<li><a href='#new-responsibilities'>
+New Responsibilities
+ </a>
+ <ul>
+<li><a href='#oversight'>
+Oversight
+ </a>
+</li>
 <li><a href='#security'>
 Security
  </a>
@@ -257,6 +265,8 @@
 </ul>
 </li>
 </ul>
+</li>
+</ul>
 </div>
 <h3>
    <a name="abstract">Abstract</a>
@@ -1325,25 +1335,75 @@
             </p>
 </div>
 <h4>
-   <a name="security">Security</a>
+   <a name="new-responsibilities">New Responsibilities</a>
 </h4>
 <div class="section-content">
-<p>
-    
-              Each project needs to be able to manage security. By their
-                      nature, these issues need to be dealt with in private. These
-                      issues may either be dealt with on a separate list or by the
-                      private list. Which list is suitable for security issues
-                      should be noted.
-    
-            </p>
-<p>
-    
-              Volunteers need to be found from the <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>
-                      to work with the Apache security team and act as first
-                      contacts on security matters.
-    
-            </p>
+<h5> 
+   <a name="oversight">Oversight</a> 
+</h5> 
+<div class="section-content">
+<p>
+                    During the stay in the Incubator, the
+                    <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">
+                      Incubator PMC (IPMC)
+                    </a>
+                    was responsible to the
+                    <a href="/incubation/Roles_and_Responsibilities.html#board">
+                      Board
+                    </a>
+                    for oversight. A graduated project must now take
+                    responsibility for it's own oversight.
+                  </p>
+<p>
+                    A project needs to ensure that it's code base is
+                    clean from an IP perspective. New committers need to
+                    recruited, educated and mentored. Quality releases
+                    need to be cut. Community spirit needs to be maintained
+                    and conflicts resolved positively. Board reports need
+                    to be accurate and prompt.
+                  </p>
+<p>
+                    Help is still available but the
+                    appropriate bodies (infrastructure, community, legal
+                    and so on) should now be approached directly.
+                  </p>
+</div>
+<h5> 
+   <a name="security">Security</a> 
+</h5> 
+<div class="section-content">
+<p>
+
+                    Each project needs to be able to manage security issues
+                    discovered in their code. By their nature, these issues 
+                    need to be dealt with in private. These issues may either 
+                    be dealt with on a separate security list or on the 
+                    private list. Which list is suitable for security issues 
+                    should be noted.
+
+                  </p>
+<p>
+
+                    Volunteers need to be found from the
+                    <a href="http://www.apache.org/foundation/how-it-works.html#structure">
+                      PMC
+                    </a>
+                    to work with the Apache security team and act as
+                    first contacts on security matters. The new project 
+                    should make contact with the team soon after graduation
+                    and not wait for the first issue to be raised.
+
+                  </p>
+<p>
+                  
+                    Projects should adopt a positive attitude towards
+                    security issues. It is easy to gain a poor reputation
+                    by mishandling of these issues. There are many people
+                    at Apache with considerable experience in this area
+                    so ask first.
+                  
+                  </p>
+</div>
 </div>
 </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