incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r536328 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Tue, 08 May 2007 21:01:45 GMT
Author: rdonkin
Date: Tue May  8 14:01:44 2007
New Revision: 536328

URL: http://svn.apache.org/viewvc?view=rev&rev=536328
Log:
Various improvements and additional content. https://issues.apache.org/jira/browse/INCUBATOR-63.
Contributed by Martijn Dashorst and Craig Russell.

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=536328&r1=536327&r2=536328
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Tue May  8 14:01:44 2007
@@ -98,7 +98,7 @@
                             </li>
                             <li>
                            Ensure mentors and IPMC have no 
-                           <a href='notes-issues'>remaining issues</a>
+                           <a href='#notes-issues'>remaining issues</a>
                             </li>
                         </ul>
                     </li>
@@ -106,7 +106,7 @@
 Decide upon <a href='#subproject-or-top-level'>destination</a>
                     </li>
                     <li>
-Prepare a <a href='#charter'>resolution</a> <em>(top level candidates only)</em>.
+Prepare a <a href='#resolution'>resolution</a> <em>(top level candidates
only)</em>.
                     </li>
                     <li>
 <a href='#subproject-acceptance'>Subproject acceptance vote</a> by destination
Project
@@ -151,9 +151,9 @@
 of the new project by the board.
                    </p>
                    <p>
-The IPMC will also express a democractic opinion. For those seeking to graduate to a subproject
+The IPMC will also express a democratic opinion. For those seeking to graduate to a subproject
 this vote is to approve the transfer. For those seeking to graduation as a top level project,
this
-will be a recommendation to the board. Expect IPMCers to ask questions about the project

+will be a recommendation to the board. Expect IPMC-ers to ask questions about the project

 including about the choice of destination. This is part of the normal process.
                    </p>
             </section>       
@@ -228,7 +228,9 @@
         </section>
         <section id='subproject'><title>Graduation To A Subproject</title>
             <p>
-            TODO: content
+                Subprojects are accepted by a Project Management Committee. 
+				The Incubator Project Management Committee needs to approve 
+				the graduation of the podling to a subproject.
             </p>
             <section id='subproject-acceptance'>
                 <title>Subproject Acceptance VOTE</title>
@@ -249,113 +251,6 @@
                 </p>
             </section>
         </section>
-        <section id='project-first-steps'>
-            <title>First Steps Outside The Incubator</title>
-            <p>
-                Graduation is the first step in what is hopefully a long
-                road. There are some issues which incubation may not
-                cover.
-            </p>
-            <section id='transfer'><title>Transferring Resources</title>
-                <p>
-When a project graduates, then the infrastructure resources (mailing lists, websites, source,
etc.) 
-need to be transferred from the Incubator to a project's new home.
-                </p>
-                <p>
- Check list:
-                </p>
-                <ol>
-                    <li>Source
-                        <ol><li>
-                        <code>svn move</code>
-                        the podling source tree
-                        </li></ol>
-                    </li>
-                    <li>
-                        Websites
-                        <ol>
-                            <li>
-Transfer the podling website
-                            <ol>
-                                <li>
-    Load the website into it's new home.
-    See <a href="http://www.apache.org/dev/#web">infra notes</a>.
-                                </li>
-                                <li>
-    Use a  <code>.htaccess</code> entry to redirect traffic from the old URLs
to the new.
-                                </li>
-                                <li>
-    Delete the podling website from <code>/www/incubator.apache.org</code> on

-    <code>people.apache.org</code>.
-                                </li>
-                            </ol></li>
-                            <li>Update the Incubator site
-                                <ol>
-                                    <li>
-Update the Incubator <a href='http://incubator.apache.org/projects/index.html'>status
page</a>
-                                    </li>
-                                    <li>
-Update the podling <a href='#notes-status'>status page</a>. 
-All sections should now be filled in including <em>EXIT</em>.
-Take some time to read carefully since this page forms the final public record for graduation.
-                                    </li>
-                                    <li>
-Remove the podling from <code>project.xml</code>
-                                    </li>
-                                    <li> 
-Regenerate the Incubator website
-                                    </li>
-                                    <li>
-Commit
-                                    </li>
-                                    <li>
-Update the Incubator website
-                                    </li>
-                                 </ol>
-                            </li>
-                            <li>Wiki
-                                <ol>
-                                    <li>
-<em>(Top level projects)</em> 
-<a href='http://www.apache.org/dev/reporting-issues.html#wiki'>request</a> a
new wiki.
-                                    </li>
-                                    <li>
- Transfer podling related content from 
- the <a href='http://wiki.apache.org/incubator/'>Incubator wiki</a> to the project
wiki
-                                    </li>
-                                </ol>
-                            </li>
-                        </ol>
-                    </li>
-                    <li>Mailing lists
-                        <ol>
-                            <li>
-<a href='http://www.apache.org/dev/reporting-issues.html#mail'>Request</a>
-that podlings lists are transferred to their new home. Any new mailing lists should
-be requested at the same time.
-                            </li>
-                        </ol>
-                    </li>
-                    <li>Issue Tracking
-                        <ol>
-                            <li>
-Check that the issue tracking system used by the podling reflects the project's new status.
-                            </li>
-                        </ol>
-                    </li>
-                </ol>
-            </section>
-            <section id='security'>
-                <title>Security</title>
-                <p>
-                    Each project needs to be able to manage security. By
-                    their nature, these issue 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>
-            </section>
-        </section>
          <section id='project-needs'>
             <title>Some Things A Project Needs To Understand</title>
             <section id='releases'>
@@ -370,15 +265,21 @@
                 </blockquote>
                  <p>
 Projects need to cut releases. Apache projects need to understand how to
-cut Apache releases. 
+cut Apache releases.
                  </p>
                  <p>
-Podlings do not need to actual publish a release to demonstrate that
+Podlings do not need to actually publish a release to demonstrate that
 they understand how to do so but creating a release that is approved
 by the <a href='incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29'>
 incubator project management committee</a> is 
 usually the simplest way to do this. 
                  </p>
+				<p>
+If you are going to cut a release (which is highly recommended), then please read 
+the <a href="releasemanagement.html">Incubator Release Management Guide</a> for
hints,
+tips and guidelines for cutting a release that will get approved by the IPMC without 
+problems.
+				</p>
             </section>
         </section>
         <section id='notes'>
@@ -397,6 +298,22 @@
             </section>
             <section id='notes-community'>
                 <title>On Community</title>
+				<p>
+One of the exit criteria is that the podling needs to have an open and diverse
+<a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community. 
+To show this to the IPMC, it can be beneficial to vote and accept a couple of 
+new contributors during incubation: this shows that you are open to accept new 
+developers and grow your community (note: this is not a requirement, but will help
+the graduation process). It will also allow you to diversify
+your community (which <em>is</em> a requirement for graduation).
+				</p>
+				<p>
+The openness of your community is not only measured by the number of accepted contributors.

+You will need to have open and respectful discussions on the open mailing list(s). You need
to
+show that you can resolve technical conflict without destroying personal relationships. If
+you can manage this, then you have shown to be a lively, active and successful community.
+				</p>
+<!--
                 <p>TODO: content on self sustaining communities; 
                 learn how to recruit developers, committers and PMCers;
                 diversity; capability to self govern 
@@ -405,6 +322,7 @@
                 without destroying personal relationship; 
                 links to community building; positive process of introspection
                 </p>
+-->
                 <section id='community-vote'>
                     <title>Community Graduation Vote</title>
                         <p>
@@ -430,9 +348,120 @@
                 <title>On Remaining Obstacles</title>
                 <p>TODO: content</p>
             </section>
-            <section id='notes-on-hand-over'><title>On The Hand Over</title>
-                <p>TODO: content</p>
-            </section>
+            <section id='notes-on-hand-over'><title>On The Handover</title>
+                <p>This is the transfer of virtual resources from the care of the IPMC
+to the care of either the new or existing top level project taking charge of the graudating
+community.</p>
+            </section>
+	        <section id='project-first-steps'>
+	            <title>First Steps Outside The Incubator</title>
+	            <p>
+	                Graduation is the first step in what is hopefully a long
+	                road. There are some issues which incubation may not
+	                cover.
+	            </p>
+	            <section id='transfer'><title>Transferring Resources</title>
+	                <p>
+	When a project graduates, then the infrastructure resources (mailing lists, websites, source,
etc.) 
+	need to be transferred from the Incubator to a project's new home.
+	                </p>
+	                <p>
+	 Check list:
+	                </p>
+	                <ol>
+	                    <li>Source
+	                        <ol><li>
+	                        <code>svn move</code>
+	                        the podling source tree
+	                        </li><li>
+Instruct committers how to <code>svn switch</code> their workspaces
+                                </li></ol>
+	                    </li>
+	                    <li>
+	                        Websites
+	                        <ol>
+	                            <li>
+	Transfer the podling website
+	                            <ol>
+	                                <li>
+	    Load the website into its new home.
+	    See <a href="http://www.apache.org/dev/#web">infra notes</a>.
+	                                </li>
+	                                <li>
+	    Use a  <code>.htaccess</code> entry to redirect traffic from the old URLs
to the new.
+	                                </li>
+	                                <li>
+	    Delete the podling website from <code>/www/incubator.apache.org</code> on

+	    <code>people.apache.org</code>.
+	                                </li>
+	                            </ol></li>
+	                            <li>Update the Incubator site
+	                                <ol>
+	                                    <li>
+	Update the Incubator <a href='http://incubator.apache.org/projects/index.html'>status
page</a>
+	                                    </li>
+	                                    <li>
+	Update the podling <a href='#notes-status'>status page</a>. 
+	All sections should now be filled in including <em>EXIT</em>.
+	Take some time to read carefully since this page forms the final public record for graduation.
+	                                    </li>
+	                                    <li>
+	Remove the podling from <code>project.xml</code>
+	                                    </li>
+	                                    <li> 
+	Regenerate the Incubator website
+	                                    </li>
+	                                    <li>
+	Commit
+	                                    </li>
+	                                    <li>
+	Update the Incubator website
+	                                    </li>
+	                                 </ol>
+	                            </li>
+	                            <li>Wiki
+	                                <ol>
+	                                    <li>
+	<em>(Top level projects)</em> 
+	<a href='http://www.apache.org/dev/reporting-issues.html#wiki'>request</a> a
new wiki.
+	                                    </li>
+	                                    <li>
+	 Transfer podling related content from 
+	 the <a href='http://wiki.apache.org/incubator/'>Incubator wiki</a> to the project
wiki
+	                                    </li>
+	                                </ol>
+	                            </li>
+	                        </ol>
+	                    </li>
+	                    <li>Mailing lists
+	                        <ol>
+	                            <li>
+	<a href='http://www.apache.org/dev/reporting-issues.html#mail'>Request</a>
+	that podlings lists are transferred to their new home. Any new mailing lists should
+	be requested at the same time.
+	                            </li>
+	                        </ol>
+	                    </li>
+	                    <li>Issue Tracking
+	                        <ol>
+	                            <li>
+	Check that the issue tracking system used by the podling reflects the project's new status.
+	                            </li>
+	                        </ol>
+	                    </li>
+	                </ol>
+	            </section>
+	            <section id='security'>
+	                <title>Security</title>
+	                <p>
+	                    Each project needs to be able to manage security. By
+	                    their nature, these issue 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>
+	            </section>
+	        </section>
         </section>
     </body>
 </document>

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=536328&r1=536327&r2=536328
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Tue May  8 14:01:44 2007
@@ -184,20 +184,6 @@
 </li>
 </ul>
 </li>
-<li><a href='#project-first-steps'>
-First Steps Outside The Incubator
- </a>
- <ul>
-<li><a href='#transfer'>
-Transferring Resources
- </a>
-</li>
-<li><a href='#security'>
-Security
- </a>
-</li>
-</ul>
-</li>
 <li><a href='#project-needs'>
 Some Things A Project Needs To Understand
  </a>
@@ -231,12 +217,26 @@
  </a>
 </li>
 <li><a href='#notes-on-hand-over'>
-On The Hand Over
+On The Handover
+ </a>
+</li>
+<li><a href='#project-first-steps'>
+First Steps Outside The Incubator
+ </a>
+ <ul>
+<li><a href='#transfer'>
+Transferring Resources
+ </a>
+</li>
+<li><a href='#security'>
+Security
  </a>
 </li>
 </ul>
 </li>
 </ul>
+</li>
+</ul>
 </div>
 <h3>
    <a name="abstract">Abstract</a>
@@ -312,7 +312,7 @@
                             </li>
                             <li>
                            Ensure mentors and IPMC have no 
-                           <a href="notes-issues">remaining issues</a>
+                           <a href="#notes-issues">remaining issues</a>
                             </li>
                         </ul>
                     </li>
@@ -320,7 +320,7 @@
 Decide upon <a href="#subproject-or-top-level">destination</a>
                     </li>
                     <li>
-Prepare a <a href="#charter">resolution</a> <em>(top level candidates only)</em>.
+Prepare a <a href="#resolution">resolution</a> <em>(top level candidates
only)</em>.
                     </li>
                     <li>
 <a href="#subproject-acceptance">Subproject acceptance vote</a> by destination
Project
@@ -369,9 +369,9 @@
 of the new project by the board.
                    </p>
 <p>
-The IPMC will also express a democractic opinion. For those seeking to graduate to a subproject
+The IPMC will also express a democratic opinion. For those seeking to graduate to a subproject
 this vote is to approve the transfer. For those seeking to graduation as a top level project,
this
-will be a recommendation to the board. Expect IPMCers to ask questions about the project

+will be a recommendation to the board. Expect IPMC-ers to ask questions about the project

 including about the choice of destination. This is part of the normal process.
                    </p>
 </div>
@@ -455,7 +455,9 @@
 </h2>
 <div class="section-content">
 <p>
-            TODO: content
+                Subprojects are accepted by a Project Management Committee. 
+				The Incubator Project Management Committee needs to approve 
+				the graduation of the podling to a subproject.
             </p>
 <h3>
    <a name="subproject-acceptance">Subproject Acceptance VOTE</a>
@@ -481,120 +483,6 @@
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
-   <a name="project-first-steps">First Steps Outside The Incubator</a>
-</h2>
-<div class="section-content">
-<p>
-                Graduation is the first step in what is hopefully a long
-                road. There are some issues which incubation may not
-                cover.
-            </p>
-<h3>
-   <a name="transfer">Transferring Resources</a>
-</h3>
-<div class="section-content">
-<p>
-When a project graduates, then the infrastructure resources (mailing lists, websites, source,
etc.) 
-need to be transferred from the Incubator to a project's new home.
-                </p>
-<p>
- Check list:
-                </p>
-<ol>
-                    <li>Source
-                        <ol><li>
-                        <code>svn move</code>
-                        the podling source tree
-                        </li></ol>
-                    </li>
-                    <li>
-                        Websites
-                        <ol>
-                            <li>
-Transfer the podling website
-                            <ol>
-                                <li>
-    Load the website into it's new home.
-    See <a href="http://www.apache.org/dev/#web">infra notes</a>.
-                                </li>
-                                <li>
-    Use a  <code>.htaccess</code> entry to redirect traffic from the old URLs
to the new.
-                                </li>
-                                <li>
-    Delete the podling website from <code>/www/incubator.apache.org</code> on

-    <code>people.apache.org</code>.
-                                </li>
-                            </ol></li>
-                            <li>Update the Incubator site
-                                <ol>
-                                    <li>
-Update the Incubator <a href="http://incubator.apache.org/projects/index.html">status
page</a>
-                                    </li>
-                                    <li>
-Update the podling <a href="#notes-status">status page</a>. 
-All sections should now be filled in including <em>EXIT</em>.
-Take some time to read carefully since this page forms the final public record for graduation.
-                                    </li>
-                                    <li>
-Remove the podling from <code>project.xml</code>
-                                    </li>
-                                    <li> 
-Regenerate the Incubator website
-                                    </li>
-                                    <li>
-Commit
-                                    </li>
-                                    <li>
-Update the Incubator website
-                                    </li>
-                                 </ol>
-                            </li>
-                            <li>Wiki
-                                <ol>
-                                    <li>
-<em>(Top level projects)</em> 
-<a href="http://www.apache.org/dev/reporting-issues.html#wiki">request</a> a
new wiki.
-                                    </li>
-                                    <li>
- Transfer podling related content from 
- the <a href="http://wiki.apache.org/incubator/">Incubator wiki</a> to the project
wiki
-                                    </li>
-                                </ol>
-                            </li>
-                        </ol>
-                    </li>
-                    <li>Mailing lists
-                        <ol>
-                            <li>
-<a href="http://www.apache.org/dev/reporting-issues.html#mail">Request</a>
-that podlings lists are transferred to their new home. Any new mailing lists should
-be requested at the same time.
-                            </li>
-                        </ol>
-                    </li>
-                    <li>Issue Tracking
-                        <ol>
-                            <li>
-Check that the issue tracking system used by the podling reflects the project's new status.
-                            </li>
-                        </ol>
-                    </li>
-                </ol>
-</div>
-<h3>
-   <a name="security">Security</a>
-</h3>
-<div class="section-content">
-<p>
-                    Each project needs to be able to manage security. By
-                    their nature, these issue 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>
-</div>
-</div>
-           <h2><img src="/images/redarrow.gif" />
    <a name="project-needs">Some Things A Project Needs To Understand</a>
 </h2>
 <div class="section-content">
@@ -612,15 +500,21 @@
                 </blockquote>
 <p>
 Projects need to cut releases. Apache projects need to understand how to
-cut Apache releases. 
+cut Apache releases.
                  </p>
 <p>
-Podlings do not need to actual publish a release to demonstrate that
+Podlings do not need to actually publish a release to demonstrate that
 they understand how to do so but creating a release that is approved
 by the <a href="incubation/Roles_and_Responsibilites.html#Incubator+Project+Management+Committee+%28PMC%29">
 incubator project management committee</a> is 
 usually the simplest way to do this. 
                  </p>
+<p>
+If you are going to cut a release (which is highly recommended), then please read 
+the <a href="releasemanagement.html">Incubator Release Management Guide</a> for
hints,
+tips and guidelines for cutting a release that will get approved by the IPMC without 
+problems.
+				</p>
 </div>
 </div>
            <h2><img src="/images/redarrow.gif" />
@@ -645,14 +539,21 @@
    <a name="notes-community">On Community</a>
 </h3>
 <div class="section-content">
-<p>TODO: content on self sustaining communities; 
-                learn how to recruit developers, committers and PMCers;
-                diversity; capability to self govern 
-                and ability to take responsibility for collective actions;
-                learn how to disagree on technical matters 
-                without destroying personal relationship; 
-                links to community building; positive process of introspection
-                </p>
+<p>
+One of the exit criteria is that the podling needs to have an open and diverse
+<a href="http://www.apache.org/foundation/glossary.html#Meritocracy">meritocratic</a>
community. 
+To show this to the IPMC, it can be beneficial to vote and accept a couple of 
+new contributors during incubation: this shows that you are open to accept new 
+developers and grow your community (note: this is not a requirement, but will help
+the graduation process). It will also allow you to diversify
+your community (which <em>is</em> a requirement for graduation).
+				</p>
+<p>
+The openness of your community is not only measured by the number of accepted contributors.

+You will need to have open and respectful discussions on the open mailing list(s). You need
to
+show that you can resolve technical conflict without destroying personal relationships. If
+you can manage this, then you have shown to be a lively, active and successful community.
+				</p>
 <h4>
    <a name="community-vote">Community Graduation Vote</a>
 </h4>
@@ -683,10 +584,128 @@
 <p>TODO: content</p>
 </div>
 <h3>
-   <a name="notes-on-hand-over">On The Hand Over</a>
+   <a name="notes-on-hand-over">On The Handover</a>
 </h3>
 <div class="section-content">
-<p>TODO: content</p>
+<p>This is the transfer of virtual resources from the care of the IPMC
+to the care of either the new or existing top level project taking charge of the graudating
+community.</p>
+</div>
+<h3>
+   <a name="project-first-steps">First Steps Outside The Incubator</a>
+</h3>
+<div class="section-content">
+<p>
+	                Graduation is the first step in what is hopefully a long
+	                road. There are some issues which incubation may not
+	                cover.
+	            </p>
+<h4>
+   <a name="transfer">Transferring Resources</a>
+</h4>
+<div class="section-content">
+<p>
+	When a project graduates, then the infrastructure resources (mailing lists, websites, source,
etc.) 
+	need to be transferred from the Incubator to a project's new home.
+	                </p>
+<p>
+	 Check list:
+	                </p>
+<ol>
+	                    <li>Source
+	                        <ol><li>
+	                        <code>svn move</code>
+	                        the podling source tree
+	                        </li><li>
+Instruct committers how to <code>svn switch</code> their workspaces
+                                </li></ol>
+	                    </li>
+	                    <li>
+	                        Websites
+	                        <ol>
+	                            <li>
+	Transfer the podling website
+	                            <ol>
+	                                <li>
+	    Load the website into its new home.
+	    See <a href="http://www.apache.org/dev/#web">infra notes</a>.
+	                                </li>
+	                                <li>
+	    Use a  <code>.htaccess</code> entry to redirect traffic from the old URLs
to the new.
+	                                </li>
+	                                <li>
+	    Delete the podling website from <code>/www/incubator.apache.org</code> on

+	    <code>people.apache.org</code>.
+	                                </li>
+	                            </ol></li>
+	                            <li>Update the Incubator site
+	                                <ol>
+	                                    <li>
+	Update the Incubator <a href="http://incubator.apache.org/projects/index.html">status
page</a>
+	                                    </li>
+	                                    <li>
+	Update the podling <a href="#notes-status">status page</a>. 
+	All sections should now be filled in including <em>EXIT</em>.
+	Take some time to read carefully since this page forms the final public record for graduation.
+	                                    </li>
+	                                    <li>
+	Remove the podling from <code>project.xml</code>
+	                                    </li>
+	                                    <li> 
+	Regenerate the Incubator website
+	                                    </li>
+	                                    <li>
+	Commit
+	                                    </li>
+	                                    <li>
+	Update the Incubator website
+	                                    </li>
+	                                 </ol>
+	                            </li>
+	                            <li>Wiki
+	                                <ol>
+	                                    <li>
+	<em>(Top level projects)</em> 
+	<a href="http://www.apache.org/dev/reporting-issues.html#wiki">request</a> a
new wiki.
+	                                    </li>
+	                                    <li>
+	 Transfer podling related content from 
+	 the <a href="http://wiki.apache.org/incubator/">Incubator wiki</a> to the project
wiki
+	                                    </li>
+	                                </ol>
+	                            </li>
+	                        </ol>
+	                    </li>
+	                    <li>Mailing lists
+	                        <ol>
+	                            <li>
+	<a href="http://www.apache.org/dev/reporting-issues.html#mail">Request</a>
+	that podlings lists are transferred to their new home. Any new mailing lists should
+	be requested at the same time.
+	                            </li>
+	                        </ol>
+	                    </li>
+	                    <li>Issue Tracking
+	                        <ol>
+	                            <li>
+	Check that the issue tracking system used by the podling reflects the project's new status.
+	                            </li>
+	                        </ol>
+	                    </li>
+	                </ol>
+</div>
+<h4>
+   <a name="security">Security</a>
+</h4>
+<div class="section-content">
+<p>
+	                    Each project needs to be able to manage security. By
+	                    their nature, these issue 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>
+</div>
 </div>
 </div>
          </td>
@@ -703,8 +722,6 @@
           <li><a href="/projects/heraldry.html">Heraldry</a></li>

           <li><a href="/projects/ivy.html">Ivy</a></li> 
           <li><a href="/projects/juice.html">JuiCE</a></li> 
-          <li><a href="/projects/log4net.html">log4net</a></li> 
-          <li><a href="/projects/log4php.html">log4php</a></li> 
           <li><a href="/projects/lokahi.html">Lokahi</a></li> 
           <li><a href="/projects/lucene.net.html">Lucene.Net</a></li>

           <li><a href="/projects/nmaven.html">NMaven</a></li> 



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


Mime
View raw message