incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r547196 - in /incubator/public/trunk: site-author/guides/graduation.xml site-publish/guides/graduation.html
Date Thu, 14 Jun 2007 10:13:04 GMT
Author: rdonkin
Date: Thu Jun 14 03:13:02 2007
New Revision: 547196

URL: http://svn.apache.org/viewvc?view=rev&rev=547196
Log:
Consistently capitalised and linked Board.

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=547196&r1=547195&r2=547196
==============================================================================
--- incubator/public/trunk/site-author/guides/graduation.xml (original)
+++ incubator/public/trunk/site-author/guides/graduation.xml Thu Jun 14 03:13:02 2007
@@ -45,6 +45,10 @@
                     the first steps that should be taken after
                     graduation.
                 </p>
+                <p>
+                    This is just a guide. Policy is stated 
+                    <a href='http://incubator.apache.org/incubation/Incubation_Policy.html'>here</a>.
+                </p>
             </section>
             <section id="background">
                 <title>Background</title>
@@ -141,7 +145,7 @@
                    <p>
 Each proposal has a <a href='incubation/Roles_and_Responsibilities#Sponsor'>Sponsor</a>.
 The identity of the Sponsor indicates the natural destination: for proposals sponsored by
the
-board or by the 
+<a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a> or by the

 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
PMC (IPMC)</a>, 
 this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
@@ -151,13 +155,15 @@
                    <p>
 Graduation as a subproject is only possible if the subproject still falls with the scope
of the project
 and requires the consent of the project <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>.

-Graduation as a project requires the formation of the new project by the board.
+Graduation as a project requires the formation of the new project by the 
+<a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
                    </p>
                    <p>
 The <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>

 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 IPMC-ers to ask questions about the project

+will be a recommendation to the <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.

+Expect IPMC-ers to ask questions about the project 
 including about the choice of destination. This is part of the normal process.
                    </p>
             </section>       
@@ -165,14 +171,17 @@
         <section id='graduate-to-top-level'>
             <title>Graduating To Top Level</title>
             <p>
-                Top level projects are created by the board. The
+                Top level projects are created by the 
+                <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
The
 <a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>Incubator
Project Management Committee (IPMC)</a> can
-                therefore only recommend to the board that the project
+                therefore only recommend to the Board that the project
                 is ready to graduate to a top level project.
             </p>
             <section id='resolution'><title>Preparing A Charter</title>
                 <p>
-                    So, in this case a suitable board resolution should
+                    So, in this case a suitable 
+                    <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>

+                    resolution should
                     be drawn up by the community advised by the mentors.
                     Committers can access the podling template for resolutions
                     in the
@@ -206,7 +215,7 @@
                     be consulted when creating this document. Projects
                     evolve over time and some deviation from the
                     original proposal may well prove acceptable. The
-                    board resolution is the ultimate definition of the
+                    resolution is the ultimate definition of the
                     scope of an Apache project. So, it is important that
                     it reflects the vision for the project as it appears on
                     the eve of graduation.
@@ -226,7 +235,9 @@
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
                     should be started by a member of the PPMC proposing that the
-<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>
recommends the resolution to the board.
+<a href='/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'>IPMC</a>

+                    recommends the resolution to the 
+                    <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.
                 </p>
             </section>
             <section id='top-level-board-proposal'><title>Submission Of The Resolution
To The Board</title>
@@ -234,17 +245,17 @@
 Top level projects are created by a resolution by the 
 <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>. Once the

 <a href='#resolution'>resolution</a> has been finalised and consensus reached,

-it should be submitted to the board. For inclusion in the agenda for the next meeting, 
+it should be submitted to the Board. For inclusion in the agenda for the next meeting, 
 the resolution should be submitted at least 72 hours before that meeting. A calendar for
meetings is 
 <a href='http://www.apache.org/foundation/board/calendar.html'>available</a>.
                 </p>
                 <p>
-Business for the board should be submitted by a post to the <code>board</code>
mailing list.
+Business for the <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>
should be submitted by a post to the <code>board</code> mailing list.
 Posting from an Apache address is recommended. Mixing public and private lists on a post
 is not recommended. 
                 </p>
                 <p>
-The board list is private. The usual 
+The <code>board</code> list is private. The usual 
 <a href='http://www.apache.org/foundation/how-it-works.html#management'>netiquette</a>

 for Apache private lists should be observed. So, it is recommended that only the podling

 and IPMC private lists are CC'd (rather than the general incubator list). Please treat 
@@ -466,14 +477,14 @@
 					<p>
 When graduating to a new project, the process is more complex. Creating a new project requires
 a <a href='http://www.apache.org/foundation/board/calendar.html'>resolution</a>
to be passed
-by the <a href='http://www.apache.org/foundation/board/'>board</a>. Usually once
this happens,
-members of the board will inform the appropriate chairs and 
+by the <a href='http://www.apache.org/foundation/board/'>Board</a>. Usually once
this happens,
+members of the Board will inform the appropriate chairs and 
 <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMCs</a>.
Occasionally, this will 
-be missed: if more than 72 hours has passed since the board meeting, it may be worth 
+be missed: if more than 72 hours has passed since the Board meeting, it may be worth 
 someone posting a polite reminder to their favorite director.
 					</p>
 					<p>
-The board resolution will appoint a Chair for the new project. The Chair will also be appointed
+The Board resolution will appoint a Chair for the new project. The Chair will also be appointed
 an <a href='http://www.apache.org/foundation/'>Officer</a> of the Apache Software
Foundation.
 This allows them access to official resources of the foundation as well as granting power
to
 act on behalf of Apache.  
@@ -483,7 +494,7 @@
 					</p>
 					<ul>
 						<li>
-Subscribe to the board mailing list
+Subscribe to the <code>board</code> mailing list
 						</li>
 						<li>
 Subscribe to the infrastructure mailing list
@@ -512,7 +523,8 @@
 							</ul>
 						</li>
 						<li>
-Work out a reporting schedule with the board. For the first three months after
+Work out a reporting schedule with the <a href='/incubation/Roles_and_Responsibilities.html#board'>Board</a>.

+For the first three months after
 graduation this will be monthly. After that, the project should slot into
 a quarterly reporting schedule.
 						</li>
@@ -524,7 +536,7 @@
 They should then be able to start assembling the new 
 <a href='http://www.apache.org/foundation/how-it-works.html#structure'>PMC</a>.

 The starting membership 
-is listed in the board resolution. However, the Chair of the new project
+is listed in the resolution. However, the Chair of the new project
 needs to ensure that private list is created and the membership subscribed.
 					</p>
 					<p>

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=547196&r1=547195&r2=547196
==============================================================================
--- incubator/public/trunk/site-publish/guides/graduation.html (original)
+++ incubator/public/trunk/site-publish/guides/graduation.html Thu Jun 14 03:13:02 2007
@@ -279,6 +279,10 @@
                     the first steps that should be taken after
                     graduation.
                 </p>
+<p>
+                    This is just a guide. Policy is stated 
+                    <a href="http://incubator.apache.org/incubation/Incubation_Policy.html">here</a>.
+                </p>
 </div>
 <h3>
    <a name="background">Background</a>
@@ -385,7 +389,7 @@
 <p>
 Each proposal has a <a href="incubation/Roles_and_Responsibilities#Sponsor">Sponsor</a>.
 The identity of the Sponsor indicates the natural destination: for proposals sponsored by
the
-board or by the 
+<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a> or by the

 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
PMC (IPMC)</a>, 
 this is a top level project; for others, this is as a subproject
 of the sponsoring project but the destination is fixed on graduation, not entry. Projects
grow
@@ -395,13 +399,15 @@
 <p>
 Graduation as a subproject is only possible if the subproject still falls with the scope
of the project
 and requires the consent of the project <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>.

-Graduation as a project requires the formation of the new project by the board.
+Graduation as a project requires the formation of the new project by the 
+<a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
                    </p>
 <p>
 The <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>

 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 IPMC-ers to ask questions about the project

+will be a recommendation to the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.

+Expect IPMC-ers to ask questions about the project 
 including about the choice of destination. This is part of the normal process.
                    </p>
 </div>
@@ -411,9 +417,10 @@
 </h2>
 <div class="section-content">
 <p>
-                Top level projects are created by the board. The
+                Top level projects are created by the 
+                <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
The
 <a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">Incubator
Project Management Committee (IPMC)</a> can
-                therefore only recommend to the board that the project
+                therefore only recommend to the Board that the project
                 is ready to graduate to a top level project.
             </p>
 <h3>
@@ -421,7 +428,9 @@
 </h3>
 <div class="section-content">
 <p>
-                    So, in this case a suitable board resolution should
+                    So, in this case a suitable 
+                    <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>

+                    resolution should
                     be drawn up by the community advised by the mentors.
                     Committers can access the podling template for resolutions
                     in the
@@ -454,7 +463,7 @@
                     be consulted when creating this document. Projects
                     evolve over time and some deviation from the
                     original proposal may well prove acceptable. The
-                    board resolution is the ultimate definition of the
+                    resolution is the ultimate definition of the
                     scope of an Apache project. So, it is important that
                     it reflects the vision for the project as it appears on
                     the eve of graduation.
@@ -476,7 +485,9 @@
                     incubator list before a vote is started to allow
                     feedback. Once a consensus has been reached, a vote
                     should be started by a member of the PPMC proposing that the
-<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>
recommends the resolution to the board.
+<a href="/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29">IPMC</a>

+                    recommends the resolution to the 
+                    <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.
                 </p>
 </div>
 <h3>
@@ -487,17 +498,17 @@
 Top level projects are created by a resolution by the 
 <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>. Once the

 <a href="#resolution">resolution</a> has been finalised and consensus reached,

-it should be submitted to the board. For inclusion in the agenda for the next meeting, 
+it should be submitted to the Board. For inclusion in the agenda for the next meeting, 
 the resolution should be submitted at least 72 hours before that meeting. A calendar for
meetings is 
 <a href="http://www.apache.org/foundation/board/calendar.html">available</a>.
                 </p>
 <p>
-Business for the board should be submitted by a post to the <code>board</code>
mailing list.
+Business for the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>
should be submitted by a post to the <code>board</code> mailing list.
 Posting from an Apache address is recommended. Mixing public and private lists on a post
 is not recommended. 
                 </p>
 <p>
-The board list is private. The usual 
+The <code>board</code> list is private. The usual 
 <a href="http://www.apache.org/foundation/how-it-works.html#management">netiquette</a>

 for Apache private lists should be observed. So, it is recommended that only the podling

 and IPMC private lists are CC'd (rather than the general incubator list). Please treat 
@@ -755,14 +766,14 @@
 <p>
 When graduating to a new project, the process is more complex. Creating a new project requires
 a <a href="http://www.apache.org/foundation/board/calendar.html">resolution</a>
to be passed
-by the <a href="http://www.apache.org/foundation/board/">board</a>. Usually once
this happens,
-members of the board will inform the appropriate chairs and 
+by the <a href="http://www.apache.org/foundation/board/">Board</a>. Usually once
this happens,
+members of the Board will inform the appropriate chairs and 
 <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMCs</a>.
Occasionally, this will 
-be missed: if more than 72 hours has passed since the board meeting, it may be worth 
+be missed: if more than 72 hours has passed since the Board meeting, it may be worth 
 someone posting a polite reminder to their favorite director.
 					</p>
 <p>
-The board resolution will appoint a Chair for the new project. The Chair will also be appointed
+The Board resolution will appoint a Chair for the new project. The Chair will also be appointed
 an <a href="http://www.apache.org/foundation/">Officer</a> of the Apache Software
Foundation.
 This allows them access to official resources of the foundation as well as granting power
to
 act on behalf of Apache.  
@@ -772,7 +783,7 @@
 					</p>
 <ul>
 						<li>
-Subscribe to the board mailing list
+Subscribe to the <code>board</code> mailing list
 						</li>
 						<li>
 Subscribe to the infrastructure mailing list
@@ -801,7 +812,8 @@
 							</ul>
 						</li>
 						<li>
-Work out a reporting schedule with the board. For the first three months after
+Work out a reporting schedule with the <a href="/incubation/Roles_and_Responsibilities.html#board">Board</a>.

+For the first three months after
 graduation this will be monthly. After that, the project should slot into
 a quarterly reporting schedule.
 						</li>
@@ -813,7 +825,7 @@
 They should then be able to start assembling the new 
 <a href="http://www.apache.org/foundation/how-it-works.html#structure">PMC</a>.

 The starting membership 
-is listed in the board resolution. However, the Chair of the new project
+is listed in the resolution. However, the Chair of the new project
 needs to ensure that private list is created and the membership subscribed.
 					</p>
 <p>



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


Mime
View raw message