incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nicola...@apache.org
Subject cvs commit: incubator-site/build/site/incubation incubation-process.png Incubation_Policy.html Incubation_Policy.pdf Process_Description.html Process_Description.pdf Roles_and_Responsibilities.html Roles_and_Responsibilities.pdf
Date Mon, 01 Dec 2003 10:18:47 GMT
nicolaken    2003/12/01 02:18:47

  Modified:    build/site/incubation Incubation_Policy.html
                        Incubation_Policy.pdf Process_Description.html
                        Process_Description.pdf
                        Roles_and_Responsibilities.html
                        Roles_and_Responsibilities.pdf
  Added:       build/site/incubation incubation-process.png
  Log:
  Update the incubation docs without draft status and new process image.
  
  Revision  Changes    Path
  1.7       +30 -42    incubator-site/build/site/incubation/Incubation_Policy.html
  
  Index: Incubation_Policy.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/incubation/Incubation_Policy.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Incubation_Policy.html	28 Nov 2003 15:49:54 -0000	1.6
  +++ Incubation_Policy.html	1 Dec 2003 10:18:47 -0000	1.7
  @@ -413,28 +413,16 @@
   </h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The incubation process covers the establishment of a candidate, acceptance (or
rejection) of a candidate leading to the potential establishment of a Podling and associated
incubation process, which ultimately leads to the establishment or a new Apache Top-Level-Project
(TLP) or sub-project within an existing Apache Project. </p>
  -<pre class="code">&#13;
  -&#13;
  -&#13;
  - establishment   |------------|  acceptance   |----------|   engagement   |----------|&#13;
  ----------------&gt; | Candidate  |-------------&gt; | Podling  |---------------&gt;|
Project  |&#13;
  -                 |------------|               |----------|--|             |----------|&#13;
  -                      |                         |  ^        |&#13;
  -                      |                         |  |        | continuation&#13;
  -                      V                         |  |--------|&#13;
  -                   rejection                    |     &#13;
  -                                                V&#13;
  -                                           termination&#13;
  -  &#13;
  -</pre>
  +<p>
  +<img alt="incubation-process.png" src="incubation-process.png"></p>
   </div>
   </div>
  -<a name="N1004D"></a><a name="Entry+to+Incubation%0D%0A"></a>
  +<a name="N1004F"></a><a name="Entry+to+Incubation%0D%0A"></a>
   <h3>Entry to Incubation&#13;
   </h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Entry to Incubation requires a number of hurdles be passed. </p>
  -<a name="N10053"></a><a name="Proposal%0D%0A"></a>
  +<a name="N10055"></a><a name="Proposal%0D%0A"></a>
   <h4>Proposal&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -454,7 +442,7 @@
   <strong>Need to provide a short list</strong> 
   </p>
   </div>
  -<a name="N1006D"></a><a name="Acceptance+of+Proposal+by+Sponsor%0D%0A"></a>
  +<a name="N1006F"></a><a name="Acceptance+of+Proposal+by+Sponsor%0D%0A"></a>
   <h4>Acceptance of Proposal by Sponsor&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -468,7 +456,7 @@
   <p>The Incubator PMC MAY immediately accept the Candidate, or may (at the discretion
of the Incubator PMC) require a successful VOTE by the Incubator PMC. </p>
   <p>The nominated Mentors MAY be immediately accepted by the Incubator PMC.  However
the Incubator PMC MAY also suggest replacement Mentors.  The Incubator PMC has the final choice
of Mentors. </p>
   </div>
  -<a name="N10080"></a><a name="Creation+of+Podling%0D%0A"></a>
  +<a name="N10082"></a><a name="Creation+of+Podling%0D%0A"></a>
   <h4>Creation of Podling&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -476,12 +464,12 @@
   <p>Upon acceptance by the Incubator PMC, the Podling's Mentor becomes a member of
the Incubator PMC (should they not already be one). </p>
   </div>
   </div>
  -<a name="N10088"></a><a name="Incubation+Activities%0D%0A"></a>
  +<a name="N1008A"></a><a name="Incubation+Activities%0D%0A"></a>
   <h3>Incubation Activities&#13;
   </h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The following sections detail the minimum activities that must be undertaken by
the various parties during an Incuabation process. </p>
  -<a name="N1008E"></a><a name="Setting+Up+a+New+Podling%0D%0A"></a>
  +<a name="N10090"></a><a name="Setting+Up+a+New+Podling%0D%0A"></a>
   <h4>Setting Up a New Podling&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -494,7 +482,7 @@
   <li>Incubator PMC mandating a helper Mentor </li>
   </ul>
   </div>
  -<a name="N1009C"></a><a name="Ongoing+Activities%0D%0A"></a>
  +<a name="N1009E"></a><a name="Ongoing+Activities%0D%0A"></a>
   <h4>Ongoing Activities&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -511,7 +499,7 @@
   </ul>
   <p>The Mentor MUST ensure that the STATUS file is up to date at all times. </p>
   </div>
  -<a name="N100B5"></a><a name="Review+of+Activity"></a>
  +<a name="N100B7"></a><a name="Review+of+Activity"></a>
   <h4>Review of Activity</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>Each Podling in Incubation SHALL undergo a regular review of progress by the Incubator
PMC.  Such reviews SHALL occur at least quaterly.  The Incubator PMC MAY, at their discretion,
choose to review individual Podlings with greater frequency.  The Incubator PMC SHALL inform
Podlings of review dates at least 4 weeks in advance. </p>
  @@ -524,7 +512,7 @@
   </ul>
   <p>Termination and Escalation are discussed in more detail in section "Exitting the
Incubator". </p>
   </div>
  -<a name="N100C8"></a><a name="Disputing+an+Assessment%0D%0A"></a>
  +<a name="N100CA"></a><a name="Disputing+an+Assessment%0D%0A"></a>
   <h4>Disputing an Assessment&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -545,7 +533,7 @@
   </ul>
   <p>The decision of the Board of the Apache Software Foundation is final. </p>
   </div>
  -<a name="N100E6"></a><a name="Continuation%0D%0A"></a>
  +<a name="N100E8"></a><a name="Continuation%0D%0A"></a>
   <h4>Continuation&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -553,12 +541,12 @@
   <p>The Mentor SHALL review the contents of the continuation recommendation and ensure
that the development recommendations are carried out over the following review period. </p>
   </div>
   </div>
  -<a name="N100EE"></a><a name="Podling+Constraints%0D%0A"></a>
  +<a name="N100F0"></a><a name="Podling+Constraints%0D%0A"></a>
   <h3>Podling Constraints&#13;
   </h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>While in Incubation, Podlings are constrained in the actions they can undertake.
</p>
  -<a name="N100F4"></a><a name="Branding%0D%0A"></a>
  +<a name="N100F6"></a><a name="Branding%0D%0A"></a>
   <h4>Branding&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -570,7 +558,7 @@
   <p>Podlings wishing to use a different disclaimer message MUST have the disclaimer
approved by the Incubator PMC prior to use. </p>
   <p>Podlings websites SHOULD contain the Apache Incubator Project logo as sign of
affiliation. </p>
   </div>
  -<a name="N10104"></a><a name="Releases%0D%0A"></a>
  +<a name="N10106"></a><a name="Releases%0D%0A"></a>
   <h4>Releases&#13;
   </h4>
   <div style="margin-left: 0 ; border: 2px">
  @@ -584,11 +572,11 @@
   <li>the release archive MUST contain an Incubation disclaimer (as described in the
previous section), clearly visible in the main documentation or README file. </li>
   </ul>
   </div>
  -<a name="N10117"></a><a name="Use+of+Apache+Resources"></a>
  +<a name="N10119"></a><a name="Use+of+Apache+Resources"></a>
   <h4>Use of Apache Resources</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The Podling is not yet an Apache project, and it should thus always refer to the
Incubator Project Resource usage Guidelines, that are as follows. </p>
  -<a name="N1011D"></a><a name="Website"></a>
  +<a name="N1011F"></a><a name="Website"></a>
   <h5>Website</h5>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -625,11 +613,11 @@
   </div>
   </div>
   </div>
  -<a name="N10149"></a><a name="Exitting+the+Incubator"></a>
  +<a name="N1014B"></a><a name="Exitting+the+Incubator"></a>
   <h3>Exitting the Incubator</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the requirements and process for exitting the Incubator.
</p>
  -<a name="N1014F"></a><a name="Minimum+Exit+Requirements"></a>
  +<a name="N10151"></a><a name="Minimum+Exit+Requirements"></a>
   <h4>Minimum Exit Requirements</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>Prior to escalation to the ASF, a Podling needs to show that : </p>
  @@ -693,27 +681,27 @@
   <li>Developers tied into ASF PGP web of trust </li>
   </ul>
   </div>
  -<a name="N101B1"></a><a name="Termination+of+a+Podling"></a>
  +<a name="N101B3"></a><a name="Termination+of+a+Podling"></a>
   <h4>Termination of a Podling</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>If you receive a recommendation for termination then you have a problem.  Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame.  A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor.  You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.  </p>
   </div>
  -<a name="N101B7"></a><a name="Migration+as+a+Top+Level+Project"></a>
  +<a name="N101B9"></a><a name="Migration+as+a+Top+Level+Project"></a>
   <h4>Migration as a Top Level Project</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>In cases where a Podling has successfully completed Incubation, and is exitting
the Incubator to become a Top Level Project, the Incubator PMC SHALL provide a recommendation
to the board that the Podling is ready to escalate.  The recommendation SHALL include a draft
resolution for the board to vote on. </p>
   </div>
  -<a name="N101BD"></a><a name="Migration+as+a+sub-project"></a>
  +<a name="N101BF"></a><a name="Migration+as+a+sub-project"></a>
   <h4>Migration as a sub-project</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>In cases where a Podling has successfully completed Incubation, and is exitting
the Incubator to become a sub-project within an already existing Top Level Project, the Incubator
PMC SHALL provide a recommendation to the TLP that the Podling is ready to escalate. </p>
   </div>
   </div>
  -<a name="N101C3"></a><a name="Roles+in+the+Incubation+Process"></a>
  +<a name="N101C5"></a><a name="Roles+in+the+Incubation+Process"></a>
   <h3>Roles in the Incubation Process</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This section describes the roles involved in the Incubation process. </p>
  -<a name="N101C9"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
  +<a name="N101CB"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
   <h4>Incubator Project Management Committee (PMC)</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html)
</p>
  @@ -729,22 +717,22 @@
   <li>be terminated. </li>
   </ul>
   </div>
  -<a name="N101E2"></a><a name="Chair+of+the+Incubator+PMC"></a>
  +<a name="N101E4"></a><a name="Chair+of+the+Incubator+PMC"></a>
   <h4>Chair of the Incubator PMC</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The person appointed by the Board of Directors to have primary responsibility
for oversight of the Incubator Project, its policies, and policy implementation. </p>
   </div>
  -<a name="N101E8"></a><a name="Candidate"></a>
  +<a name="N101EA"></a><a name="Candidate"></a>
   <h4>Candidate</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A project that is proposed for incubation. </p>
   </div>
  -<a name="N101EE"></a><a name="Champion"></a>
  +<a name="N101F0"></a><a name="Champion"></a>
   <h4>Champion</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Member of the Apache Software Foundation who supports a Candidate's application
for Incubation and who supports and assists the Podling through the Incubation process. </p>
   </div>
  -<a name="N101F4"></a><a name="Sponsor"></a>
  +<a name="N101F6"></a><a name="Sponsor"></a>
   <h4>Sponsor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The Sponsor is the entity within the ASF that makes the determination that a candidate
would make a worthy addition to the ASF, and agrees to take on the candidate in question (or
in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation
process. </p>
  @@ -755,12 +743,12 @@
   <li>The Incubator PMC.  In this case, the Incubator PMC agrees that the project in
question will make a good addition to the ASF, but there is no clear "owner" of the candidate
should it successfully complete incubation.  An incubation exit requirement for such candidates
will be the identification (and successfuly lobbying) of an "owner" entity - either the board
(and the candidate will be a TLP) or another project. </li>
   </ul>
   </div>
  -<a name="N10203"></a><a name="Mentor"></a>
  +<a name="N10205"></a><a name="Mentor"></a>
   <h4>Mentor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Mentor is a role undertaken by a permanent member of the Apache Software Foundation
and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above).
 Upon acceptance by the Incubator PMC, the Mentor automatically becomes a member of the Incubator
PMC.  A Mentor has specific responsibilities towards the Incubator PMC, the Sponsor and towards
the members of the assigned Podling. </p>
   </div>
  -<a name="N10209"></a><a name="Committers"></a>
  +<a name="N1020B"></a><a name="Committers"></a>
   <h4>Committers</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The candidate shall declare an initial set of committers.  On acceptance of a
candidate project, the assigned Mentor shall be given access to the Podling's cvs repository
for the duration of the incubation process.  This is to allow the Mentor to perform their
incubation duties, and is for administrative purposes only.  To be given full committer privileges,
such as the right to add new code to the repository, the Mentor must earn them as would any
other potential new committer.  In some cases, the Mentor may be part of the initial set of
declared committers, but this is not a requirement of the Incubation process. </p>
  
  
  
  1.6       +148 -148  incubator-site/build/site/incubation/Incubation_Policy.pdf
  
  	<<Binary file>>
  
  
  1.7       +9 -20     incubator-site/build/site/incubation/Process_Description.html
  
  Index: Process_Description.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/incubation/Process_Description.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Process_Description.html	28 Nov 2003 15:49:54 -0000	1.6
  +++ Process_Description.html	1 Dec 2003 10:18:47 -0000	1.7
  @@ -276,21 +276,10 @@
   <h3>The Process of Incubation</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>The incubation process covers the establishment of a candidate, acceptance (or
rejection) of a candidate leading to the potential establishment of a Podling and associated
incubation process, which ultimately leads to the establishment or a new Apache Top-Level-Project
(TLP) or sub-project within an existing Apache Project. </p>
  -<pre class="code">&#13;
  -&#13;
  - establishment   |------------|  acceptance   |----------|   engagement   |----------|&#13;
  ----------------&gt; | Candidate  |-------------&gt; | Podling  |---------------&gt;|
Project  |&#13;
  -                 |------------|               |----------|--|             |----------|&#13;
  -                      |                         |  ^        |&#13;
  -                      |                         |  |        | continuation&#13;
  -                      V                         |  |--------|&#13;
  -                   rejection                    |     &#13;
  -                                                V&#13;
  -                                           termination&#13;
  -  &#13;
  -</pre>
  -<p>Readers should also review the  <a href="Roles_and_Responsibilities.html">Roles
and Responsibilities </a>document for a description of the various parties involved
in the Incubation process. </p>
  -<a name="N10015"></a><a name="Establishment"></a>
  +<p>
  +<img alt="incubation-process.png" src="incubation-process.png"></p>
  +<p>Readers should also review the  <a href="../incubation/Roles_and_Responsibilities.html">Roles
and Responsibilities </a>document for a description of the various parties involved
in the Incubation process. </p>
  +<a name="N10017"></a><a name="Establishment"></a>
   <h4>Establishment</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The first thing you will want to do is find a  <strong>Champion </strong>
for your project.  One way to do this is to explore the Apache site to find similar projects.
 Spend some time reading both the projects' web pages and mailing lists.  By simply lurking
on the mailing lists (see Mailing Lists section  in this document), you may get ideas about
who you would like to ask to help you with your project proposal.  However, Champions must
either be ASF   <a href="http://www.apache.org/foundation/members.html">members </a>or
 <a href="http://www.apache.org/foundation/index.html">officers </a>(see the Champion
section later in this document for more on Champion criteria and responsibilities).  Once
you have found an eligible person who is willing to act as Champion, you can use this person
to help you determine if and how your proposal can complement the ASF.  If you and your Champion
are convinced that your candidate project would fit with the "Apache Way", your Champion can
help you to get it established. </p>
  @@ -298,7 +287,7 @@
   <p>A  <strong>Candidate </strong> project description should be submitted
to the relevant mailing list(s) of a  <strong>Sponsor </strong> (see the Mailing
Lists section in this document).  See the  <a href="http://jakarta.apache.org/site/newproject.html">Jakarta
Guidelines for New Projects </a>for a list of issues that should be addressed in your
proposal; also see  <a href="http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages">ASF
Proposal Pages </a>for other examples.  Typically a  <strong>Candidate </strong>
is submitted under a message tagged with [[PROPOSAL].  Such a message will normally trigger
some discussions on the receiving mailing list(s).  Your Champion will be involved in these
discussions acting as your advocate. </p>
   <p>As a proposer you should consider the feedback and attempt to gauge a sense of
consensus.  Do not be put off by extended threads under your initial post that have little
or nothing to do with you proposal - however, if you feel that your candidate project is not
being addresed you may want to specifically request a decision on the Candidate by the Sponsor
by posting a request to the decision making list (either pmc@{project-name}.apache.org or
board@apache.org; see Mailing List section for more details).  Sometimes a vote will be announced
without you asking for it (perhaps you have done some homework and have a PMC member assisting
you though the process), other times you may need to cut through discussions and push your
request forward for a decision. </p>
   </div>
  -<a name="N10040"></a><a name="Acceptance"></a>
  +<a name="N10042"></a><a name="Acceptance"></a>
   <h4>Acceptance</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The decision to accept a project is taken on a vote by the Sponsor.  The format
of this vote will depend on the rules of the entity in question.  Here again it helps if you
have a PMC Member (or board member if the Sponsor is the ASF board) aligned with your project
(preferably as your Champion) because you stand a better chance of getting feedback about
what is actually happening.  The Sponsor will typically take about 7-10 days before announcing
a vote result.   </p>
  @@ -307,7 +296,7 @@
   <p>One of the roles of the Mentor is to keep away the wolves - and in the case of
incubation the wolf is the Incubator PMC, the policies, the process, and inevitable bureaucracy
and delays.  The Mentor can help you by guiding and protecting you from much of this based
on his/her experience in the process and familiarity with the policy and procedures of incubation.
 In performing their role, the Mentor is representing the Sponsor.   </p>
   <p>Your Sponsor, represented by your Mentor, has specific responsibilities towards
you and the Incubator PMC.  There are a bunch of administrative and technical actions to take
care of.  Your Mentor is responsible for ensuring that these things happen quickly and efficiently.
 Also, your Mentor is going to help you out with the getting in place of the policies and
procedures you use for introducing new comitters, decision making, etc.  These aspects will
be watched closely by the Incubator PMC as they provide a good indication of community dynamics,
health and correlation with Apache practices. </p>
   </div>
  -<a name="N10057"></a><a name="Review"></a>
  +<a name="N10059"></a><a name="Review"></a>
   <h4>Review</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>As your project sorts things out and things stabilize (infrastructure, communications,
decision making) you will inevitably come under an assessment by the Incubator PMC concerning
the exit of your project from the incubator.  Keep in mind that exit can be a good things
and bad thing.  Exit via escalation to a top-level project or perhaps a subproject of an existing
PMC would typically be viewed as a positive exit.  On the other-hand, termination is also
an exit condition that may be considered.  With an upcoming assessment it is generally a good
idea to have your STATUS file right up to-date and to ensure that your Mentor is doing his/her
job of evangelizing your project and has good picture of where you are relative to acceptance
or the last assessment point.  This information will help the Incubator PMC to recommend the
best action for for your project.   </p>
  @@ -319,17 +308,17 @@
   </ul>
   <p>Note that whilst this is a recommendation, it carries a lot of weight.  A Sponsor
will only over-ride the recommendation of the Incubator in exceptional circumstances, and
even then it is likely that the issue in question would be escalated to the ASF board for
their consideration. </p>
   </div>
  -<a name="N10068"></a><a name="Termination"></a>
  +<a name="N1006A"></a><a name="Termination"></a>
   <h4>Termination</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>If you receive a recommendation for termination then you have a problem.  Chances
are that there are either legal or structural problems with your project that in the opinion
of the Incubator PMC are not resolvable within a reasonable time frame.  A termination decision
is basically time to close down the project. However, you do have the right to appeal a termination
decision with the Board of Directors and/or your Sponsor.  You should be aware that several
Members of the Board are also Members of the Incubator PMC and as such, an appeal is unlikely
to be successful.  </p>
   </div>
  -<a name="N1006E"></a><a name="Continuation"></a>
  +<a name="N10070"></a><a name="Continuation"></a>
   <h4>Continuation</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A recommendation by the Incubator PMC for continuation of incubation shall include
development recommendations. The Incubator PMC has a responsibility to ensure that the recommended
actions are tangible and quantifiable.  For example, an assessment could be that your project
has not established a sufficient community to be viable, in which case the Incubator PMC is
obliged to state specific targets that they consider as viable.  This does not necessarily
mean that if you meet this target by the next review that you are out of incubation - but
it does give you concrete achievements that you can site. Your Mentor is also specifically
accountable to you for ensuring that the recommendations for continuation are usable, substantive
and tangible. If this is not the case, you have every right to appeal an Incubator decision
to the Apache Board. However, if your Mentor is doing a good job, neither of these scenarios
should arise. </p>
   </div>
  -<a name="N10074"></a><a name="Escalation"></a>
  +<a name="N10076"></a><a name="Escalation"></a>
   <h4>Escalation</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>For Podlings that aim to establish sub-projects or products within existing communities
you are almost home-free. The main issues you need to deal with now is migration of you code
into the target project, something you should be confident in doing based on the contacts
and understanding you gained during initial establishment and incubation.   </p>
  
  
  
  1.5       +140 -154  incubator-site/build/site/incubation/Process_Description.pdf
  
  	<<Binary file>>
  
  
  1.7       +10 -13    incubator-site/build/site/incubation/Roles_and_Responsibilities.html
  
  Index: Roles_and_Responsibilities.html
  ===================================================================
  RCS file: /home/cvs/incubator-site/build/site/incubation/Roles_and_Responsibilities.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- Roles_and_Responsibilities.html	28 Nov 2003 15:49:54 -0000	1.6
  +++ Roles_and_Responsibilities.html	1 Dec 2003 10:18:47 -0000	1.7
  @@ -275,11 +275,8 @@
   <a name="N10007"></a><a name="Roles+and+Responsibilities"></a>
   <h3>Roles and Responsibilities</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>
  -<strong>This is currently a draft, and has no official status.</strong> 
  -</p>
   <p>This document describes the roles (including Sponsor, Contributor, Mentor) and
provides an overview of the responsibilities of the different parties involved in an incubation
process. </p>
  -<a name="N10011"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
  +<a name="N1000D"></a><a name="Incubator+Project+Management+Committee+%28PMC%29"></a>
   <h4>Incubator Project Management Committee (PMC)</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>(From the resolution that created the Incubator Project - see http://incubator.apache.org/resolution.html)
</p>
  @@ -298,12 +295,12 @@
   <p>A project going through the Incubator will therefore be required to regularly
report to the Incubator PMC.  This will help the PMC in its role of reviewing the status of
a project under incubation. </p>
   <p>Finally, the Incubator PMC is the ASF body with the greatest level of expertise
and experience in the Incubation process.  They provide a store of knowledge that can be called
on by the Mentor or a Podling during (or even after) the incubation process.  In cases where
an Incubation is particularly large, or where the Incubator PMC otherwise feels the Mentor
needs additional assistance, the Incubator PMC may choose to provide an experienced Mentor
to assist the main Mentor in discharging their duty. </p>
   </div>
  -<a name="N10030"></a><a name="Chair+of+the+Incubator+PMC"></a>
  +<a name="N1002C"></a><a name="Chair+of+the+Incubator+PMC"></a>
   <h4>Chair of the Incubator PMC</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The person appointed by the Board of Directors to have primary responsibility
for oversight of the Incubator Project, its policies, and policy implementation. </p>
   </div>
  -<a name="N10036"></a><a name="Candidate"></a>
  +<a name="N10032"></a><a name="Candidate"></a>
   <h4>Candidate</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Candidate is a project that is proposed for incubation. A Candidate shall meet
the following minimum criteria: </p>
  @@ -319,14 +316,14 @@
   <p>Naturally, projects will need more than this in order to exit incubation status.
</p>
   <p>A candidate project compliant with the above criteria may be proposed by the Champion
to the Sponsor for acceptance as a Podling.  Acceptance of a candidate shall be subject to
the formal voting method of the Sponsor.  Should that vote be accepted, the Sponsor will request
that the Incubator PMC accept the candidate as a Podling under incubation.  The Sponsor shall
assign a Mentor, who shall be granted membership of the Incubator PMC for the duration of
the incubation process. </p>
   </div>
  -<a name="N1004C"></a><a name="Champion"></a>
  +<a name="N10048"></a><a name="Champion"></a>
   <h4>Champion</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A candidate project shall be sponsored by an  <a href="http://www.apache.org/foundation/index.html">Officer
</a>or  <a href="http://www.apache.org/foundation/members.html">Member </a>of
the Foundation.  The Champion assists the candidate on their initial submission to a Sponsor.
 While private conversations are not generally encouraged within the Apache community, the
Champion's relationship with the Candidate should allow for this in order to educate the Candidate
about the Apache Way and prepare the project for the questions and issues likely to be raised
by the community.  </p>
   <p>Where the Champion is not a Member of the Foundation (i.e. is an Officer only),
the Champion shall be a member of the PMC of the Sponsor. </p>
   <p>While the Champion has no formal responsibility within the Incubation process
(other than to review and comment on a Candidate's proposal within the Sponsor), it is expected
that they will play an active role.  A lack of interest on the part of a Champion may be seen
by the Incubator PMC as a negative indicator during the course of incubation. </p>
   </div>
  -<a name="N1005E"></a><a name="Sponsor"></a>
  +<a name="N1005A"></a><a name="Sponsor"></a>
   <h4>Sponsor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The Sponsor is the entity within the ASF that makes the determination that a candidate
would make a worthy addition to the ASF, and agrees to take on the candidate in question (or
in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation
process. </p>
  @@ -338,7 +335,7 @@
   </ul>
   <p>Note that a Sponsor is more than just a final resting place for a candidate that
successfully completes incubation.  The Sponsor, by taking on a candidate, is indicating that
they believe the candidate will make a worthy addition to the ASF, and takes responsibility
for assisting the podling through the Incubation process.  The Sponsor is therefore expected
to be actively involved in the incubation process and assist where necessary, giving the podling
the best possible chance of success.  In addition, an entity that is a Top Level Project should
be involved in the Candidate's incubation in order to educate the Candidate about practices
that are specific to that TLP and about other relevant projects within the TLP. </p>
   <p>However, while the Sponsor is expected to be actively involved, it is formally
representated by the Mentor.  The Mentor is the individual accountable to the Incubator PMC
for ensuring the incubation process is correctly followed.  In cases where the Mentor is not
fulfilling their responsibilities, the Sponsor (in particular its Chair) will be expected
to remedy the situation. </p>
  -<a name="N10071"></a><a name="Responsibilities+of+the+Sponsor"></a>
  +<a name="N1006D"></a><a name="Responsibilities+of+the+Sponsor"></a>
   <h5>Responsibilities of the Sponsor</h5>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -347,11 +344,11 @@
   </ul>
   </div>
   </div>
  -<a name="N1007A"></a><a name="Mentor"></a>
  +<a name="N10076"></a><a name="Mentor"></a>
   <h4>Mentor</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>A Mentor is a role undertaken by a permanent member of the Apache Software Foundation
and is chosen by the Sponsor to actively lead in the discharge of their duties (listed above).
 Upon acceptance by the Incubator PMC, the Mentor automatically becomes a member of the Incubator
PMC.  A Mentor has specific responsibilities towards the Incubator PMC, the Sponsor and towards
the members of the assigned Podling. </p>
  -<a name="N10080"></a><a name="Responsibilities+towards+Podling+Members"></a>
  +<a name="N1007C"></a><a name="Responsibilities+towards+Podling+Members"></a>
   <h5>Responsibilities towards Podling Members</h5>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -363,7 +360,7 @@
   <li>to provide where and as appropriate, guidance on matters concerning Apache policies
and practices - including the establishment of its internal steering committee. </li>
   </ul>
   </div>
  -<a name="N10091"></a><a name="Responsibilities+towards+the+Incubator+PMC"></a>
  +<a name="N1008D"></a><a name="Responsibilities+towards+the+Incubator+PMC"></a>
   <h5>Responsibilities towards the Incubator PMC</h5>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -374,7 +371,7 @@
   <li>to provide updates to the Incubator PMC and Sponsor on the status of license
grants (where and as appropriate) and other relevant legal information pertaining to the Podling.
</li>
   </ul>
   </div>
  -<a name="N100A0"></a><a name="Committers"></a>
  +<a name="N1009C"></a><a name="Committers"></a>
   <h5>Committers</h5>
   <div style="margin-left: 0 ; border: 2px">
   <p>The candidate shall declare an initial set of committers.  On acceptance of a
candidate project, the assigned Mentor shall be given access to the Podling's cvs repository
for the duration of the incubation process.  This is to allow the Mentor to perform their
incubation duties, and is for administrative purposes only.  To be given full committer privileges,
such as the right to add new code to the repository, the Mentor must earn them as would any
other potential new committer.  In some cases, the Mentor may be part of the initial set of
declared committers, but this is not a requirement of the Incubation process. </p>
  
  
  
  1.5       +66 -66    incubator-site/build/site/incubation/Roles_and_Responsibilities.pdf
  
  	<<Binary file>>
  
  
  1.1                  incubator-site/build/site/incubation/incubation-process.png
  
  	<<Binary file>>
  
  

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


Mime
View raw message