blautenb    2003/10/24 21:43:58

  Modified:    site/incubation Incubation_Policy.cwiki
                        Process_Description.cwiki
                        Roles_and_Responsibilities.cwiki
  Log:
  Consistent use of Sponsor/Champion/Mentor
  
  Revision  Changes    Path
  1.2       +17 -17    incubator/site/incubation/Incubation_Policy.cwiki
  
  Index: Incubation_Policy.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/incubation/Incubation_Policy.cwiki,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- Incubation_Policy.cwiki   16 Oct 2003 15:28:42 -0000      1.1
  +++ Incubation_Policy.cwiki   25 Oct 2003 04:43:58 -0000      1.2
  @@ -73,28 +73,28 @@
   
   In order to enter the Incubator, a Candidate MUST 
   
  -* be nominated for incubation by a member of the Apache Software Foundation 
("The Sponsor"); and
  -* be approved by a Sponsoring Entity.  
  +* be nominated for incubation by a member of the Apache Software Foundation 
("The Champion"); and
  +* be approved by a Sponsor.  
   
  -Approval by a Sponsoring Entity will generally occur only after a vote 
within the Entity, and will require that the Entity be convinced that the 
Candidate is appropriate for Incubation.  A Sponsoring Entity may be one of:
  +Approval by a Sponsor will generally occur only after a vote within the 
Entity, and will require that the Entity be convinced that the Candidate is 
appropriate for Incubation.  A Sponsor may be one of:
   
   * the Board of the Apache Software Foundation;
   * a Top Level Project (TLP) within the Apache Software Foundation (where the 
TLP considers the Candidate to be a suitable sub-project); or
   * the Incubator PMC.
   
  -To start this process, a Candidate SHOULD submit a proposal to a Sponsoring 
Entity.  The Proposal SHOULD, at minimum, detail the following areas :
  +To start this process, a Candidate SHOULD submit a proposal to a Sponsor.  
The Proposal SHOULD, at minimum, detail the following areas :
   
   __Need to provide a short list__
   
  -!!Acceptance of Proposal by Sponsoring Entity
  +!!Acceptance of Proposal by Sponsor
   
  -The decision to accept a project MUST be taken on a vote by the Sponsoring 
Entity, in accordance with that Entity's charter.  
  +The decision to accept a project MUST be taken on a vote by the Sponsor, in 
accordance with that Entity's charter.  
   
  -Upon a successful result, the Sponsoring Entity SHOULD request the Incubator 
PMC take on the Candidate as a new Podling.  The request to the Incubator PMC 
MUST contain the following information :
  +Upon a successful result, the Sponsor SHOULD request the Incubator PMC take 
on the Candidate as a new Podling.  The request to the Incubator PMC MUST 
contain the following information :
   
   * a reference to the results of the vote (so as to provide an audit trail 
for the records);
   * a reference to the Candidate's proposal;
  -* the Mentor, nominated by the Sponsoring Entity, who will guide the 
Candidate through the Incubation Process.  The nominated Mentor MUST be a 
member of the Apache Software Foundation.
  +* the Mentor, nominated by the Sponsor, who will guide the Candidate through 
the Incubation Process.  The nominated Mentor MUST be a member of the Apache 
Software Foundation.
   
   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.
   
  @@ -183,7 +183,7 @@
   
   Podlings SHOULD use the following text for all disclaimers :
   
  -''<project name> is an effort undergoing incubation at the Apache Software 
Foundation (ASF), sponsored by the <name of sponsoring entity>.  Incubation is 
required of all newly accepted projects until a further review indicates that 
the infrastructure, communications, and decision making process have stabilized 
in a manner consistent with other successful ASF projects. While incubation 
status is not necessarily a reflection of the completeness or stability of the 
code, it does indicate that the project has yet to be fully endorsed by the 
ASF.''
  +''<project name> is an effort undergoing incubation at the Apache Software 
Foundation (ASF), sponsored by the <name of sponsor>.  Incubation is required 
of all newly accepted projects until a further review indicates that the 
infrastructure, communications, and decision making process have stabilized in 
a manner consistent with other successful ASF projects. While incubation status 
is not necessarily a reflection of the completeness or stability of the code, 
it does indicate that the project has yet to be fully endorsed by the ASF.''
   
   
   Podlings wishing to use a different disclaimer message MUST have the 
disclaimer approved by the Incubator PMC prior to use.
  @@ -222,7 +222,7 @@
   
   This is achieved by imposing a set of Exit Criteria that, when met, will 
demonstrate these objectives.
   
  -Therefore, to successfully exit the Incubator and be escalated fully into 
the ASF, a Podling SHALL meet the minimum exit requirements detailed below.  
The Incubator PMC MAY set additional requirements at their discretion.  Such 
additional requirements MAY be proposed by the Mentor or the Sponsoring Entity, 
however only the Incubator PMC is authorised to formally place such 
requirements on a Podling.
  +Therefore, to successfully exit the Incubator and be escalated fully into 
the ASF, a Podling SHALL meet the minimum exit requirements detailed below.  
The Incubator PMC MAY set additional requirements at their discretion.  Such 
additional requirements MAY be proposed by the Mentor or the Sponsor, however 
only the Incubator PMC is authorised to formally place such requirements on a 
Podling.
   
   The minimum requirements that a Podling SHALL meet prior to being 
successfully escalated to the ASF are :
   
  @@ -263,7 +263,7 @@
   
   !!Termination of a Podling
   
  -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 Sponsoring Entity.  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. 
  +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. 
   
   !!Migration as a Top Level Project
   
  @@ -287,7 +287,7 @@
   * providing guidance and ensuring that sub-projects under it's purview 
develop products according to the Foundation's philosophy and guidelines for 
collaborative development;
   * providing a repository for the storage of incubation history and 
information;
   * assisting a Podling's Mentor in discharging her/his duties;
  -* regularly evaluating projects under its purview for the purposes of 
recommending to the Sponsoring Entity whether the project should:
  +* regularly evaluating projects under its purview for the purposes of 
recommending to the Sponsor whether the project should:
   ** successfully exit incubation;
   ** continue to receive guidance and support within the Incubator; or
   ** be terminated.
  @@ -301,15 +301,15 @@
   
   A project that is proposed for incubation.
   
  -!!Sponsor
  +!!Champion
   
   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.
   
  -!!Sponsoring Entity
  +!!Sponsor
   
  -The Sponsoring Entity 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.
  +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.
   
  -A Sponsoring Entity will be one of:
  +A Sponsor will be one of:
   
   * The Board of the Apache Software Foundation.  In this case, it is expected 
that the candidate would become a TLP on successful completion of Incubation.
   * A Top Level Project within the ASF.  In this case, the project in question 
has agreed that the candidate is a good fit for their project, and will take on 
the candidate as a sub-project upon successful completion of Incubation.
  @@ -317,7 +317,7 @@
   
   !!Mentor
   
  -A Mentor is a role undertaken by a permanent member of the Apache Software 
Foundation and is chosen by the Sponsoring Entity 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 Sponsoring Entity 
and towards the members of the assigned Podling.
  +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.
   
   
   !!Committers
  
  
  
  1.2       +15 -15    incubator/site/incubation/Process_Description.cwiki
  
  Index: Process_Description.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/incubation/Process_Description.cwiki,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- Process_Description.cwiki 16 Oct 2003 15:28:42 -0000      1.1
  +++ Process_Description.cwiki 25 Oct 2003 04:43:58 -0000      1.2
  @@ -24,51 +24,51 @@
   
   !!!Establishment
   
  -The first thing you will want to do is find a __Sponsor __ 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, Sponsors must either be ASF  [members 
|http://www.apache.org/foundation/members.html]  or [officers 
|http://www.apache.org/foundation/index.html] (see the Sponsor section later in 
this document for more on Sponsor criteria and responsibilities).  Once you 
have found an eligible person who is willing to act as sponsor, you can use 
this person to help you determine if and how your proposal can complement the 
ASF.  If you and your Sponsor are convinced that your candidate project would 
fit with the "Apache Way", your Sponsor can help you to get it established.
  +The first thing you will want to do is find a __Champion __ 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  [members 
|http://www.apache.org/foundation/members.html]  or [officers 
|http://www.apache.org/foundation/index.html] (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.
   
  -The establishment of a candidate involves the preparation of a project 
description (consistent with the candidate description detailed below) endorsed 
by a __Sponsor__.  
  +The establishment of a candidate involves the preparation of a project 
description (consistent with the candidate description detailed below) endorsed 
by a __Champion__.  
   
  -A __Candidate __ project description should be submitted to the relevant 
mailing list(s) of a __Sponsoring Entity __ (see the Mailing Lists section in 
this document).  See the [Jakarta Guidelines for New Projects 
|http://jakarta.apache.org/site/newproject.html] for a list of issues that 
should be addressed in your proposal; also see [ASF Proposal Pages 
|http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages] for other 
examples.  Typically a __Candidate __ is submitted under a message tagged with 
[[PROPOSAL].  Such a message will normally trigger some discussions on the 
receiving mailing list(s).  Your Sponsor will be involved in these discussions 
acting as your advocate.
  +A __Candidate __ project description should be submitted to the relevant 
mailing list(s) of a __Sponsor __ (see the Mailing Lists section in this 
document).  See the [Jakarta Guidelines for New Projects 
|http://jakarta.apache.org/site/newproject.html] for a list of issues that 
should be addressed in your proposal; also see [ASF Proposal Pages 
|http://nagoya.apache.org/wiki/apachewiki.cgi?ASFProposalPages] for other 
examples.  Typically a __Candidate __ 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.
   
  -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 Sponsoring Entity by posting a 
request to the decision making list (either [EMAIL PROTECTED] or [EMAIL 
PROTECTED]; 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.
  +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 [EMAIL PROTECTED] or [EMAIL PROTECTED]; 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.
   
   !!! Acceptance
   
  -The decision to accept a project is taken on a vote by the Sponsoring 
Entity.  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 
Sponsoring Entity is the ASF board) aligned with your project (preferably as 
your sponsor) because you stand a better chance of getting feedback about what 
is actually happening.  The Sponsoring Entity will typically take about 7-10 
days before announcing a vote result.  
  +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.  
   
  -If that vote is affirmative, the Sponsoring Entity will propose to the 
__Incubator PMC __ (referencing the voting result e-mail) that your candidate 
project be escalated to __Podling __ status.  The Sponsoring Entity will assign 
a __Shepherd __.  The Shepherd may, or may not, be your original Sponsor.  If 
not, it is expected your Sponsor will remain involved during the rest of the 
Incubation process, providing as much assistance as possible.
  +If that vote is affirmative, the Sponsor will propose to the __Incubator PMC 
__ (referencing the voting result e-mail) that your candidate project be 
escalated to __Podling __ status.  The Sponsor will assign a __Mentor __.  The 
Mentor may, or may not, be your original Champion.  If not, it is expected your 
Champion will remain involved during the rest of the Incubation process, 
providing as much assistance as possible.
   
  -The Shepherd is there to protect you, but be warned - the Shepherd is also 
holding a big stick. The Shepherd is automatically made a member of the 
Incubator PMC, and reports to both it and the Sponsoring Entity on your overall 
health and suitability for eventual inclusion within the Apache Community (or 
recommendation to terminate).  However, the Shepherd (with the assistance of 
the Sponsor) is also looking after you through the incubation.   
  +The Mentor is there to protect you, but be warned - the Mentor is also 
holding a big stick. The Mentor is automatically made a member of the Incubator 
PMC, and reports to both it and the Sponsor on your overall health and 
suitability for eventual inclusion within the Apache Community (or 
recommendation to terminate).  However, the Mentor (with the assistance of the 
Champion) is also looking after you through the incubation.   
   
  -One of the roles of the Shepherd 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 Shepherd 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 Shepherd is representing the Sponsoring Entity.  
  +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.  
   
  -Your Sponsoring Entity, represented by your Shepherd, has specific 
responsibilities towards you and the Incubator PMC.  There are a bunch of 
administrative and technical actions to take care of.  Your Shepherd is 
responsible for ensuring that these things happen quickly and efficiently.  
Also, your Shepherd 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.
  +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.
   
   !!!Review
   
  -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 Shepherd 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.  
  +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.  
   
  -Conclusion of a review process will be a recommendation (to the Sponsoring 
Entity) of one of the following:
  +Conclusion of a review process will be a recommendation (to the Sponsor) of 
one of the following:
   
   * termination;
   * continuation under incubation with recommendations; or
   * exit via escalation into Apache.
   
  -Note that whilst this is a recommendation, it carries a lot of weight.  A 
Sponsoring Entity 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.
  +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.
   
   !!Termination
   
  -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 Sponsoring Entity.  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. 
  +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. 
   
   !!Continuation
   
  -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 Shepherd 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 Shepherd is doing a good job, neither of 
these scenarios should arise.
  +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.
   
   !!Escalation
   
   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.  
   
  -For projects aiming to be a Top-Level-Project (TLP), you have an additional 
obstacle - namely the ASF Board.  While the ASF Board might be your sponsoring 
entity, this does not mean they have formally accepted you as a TLP.  To 
establish a TLP you need to draft a board motion that identifies the project 
scope, mission and charter.  You can submit the motion to the Board using the 
[EMAIL PROTECTED] email address.  Well-prepared projects will have already 
developed contacts with members of the Board so this should not be a surprise 
agenda item.  Keep in mind that the Board can approve your motion as supplied, 
amend it, or reject it.  If you are rejected then you need to sort this out 
with the Incubator PMC and allies you have developed during the incubation 
process - i.e. for a TLP objective the Incubator PMC OK is only half of the 
story.  
  +For projects aiming to be a Top-Level-Project (TLP), you have an additional 
obstacle - namely the ASF Board.  While the ASF Board might be your Sponsor, 
this does not mean they have formally accepted you as a TLP.  To establish a 
TLP you need to draft a board motion that identifies the project scope, mission 
and charter.  You can submit the motion to the Board using the [EMAIL 
PROTECTED] email address.  Well-prepared projects will have already developed 
contacts with members of the Board so this should not be a surprise agenda 
item.  Keep in mind that the Board can approve your motion as supplied, amend 
it, or reject it.  If you are rejected then you need to sort this out with the 
Incubator PMC and allies you have developed during the incubation process - 
i.e. for a TLP objective the Incubator PMC OK is only half of the story.  
   
   However, in practice, assuming you are building contacts with members in 
Apache, the Incubator PMC, and the ASF Board - the transition from Podling to 
TLP should be a smooth and painless process.
   
  
  
  
  1.2       +26 -26    
incubator/site/incubation/Roles_and_Responsibilities.cwiki
  
  Index: Roles_and_Responsibilities.cwiki
  ===================================================================
  RCS file: 
/home/cvs/incubator/site/incubation/Roles_and_Responsibilities.cwiki,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- Roles_and_Responsibilities.cwiki  16 Oct 2003 15:28:42 -0000      1.1
  +++ Roles_and_Responsibilities.cwiki  25 Oct 2003 04:43:58 -0000      1.2
  @@ -2,7 +2,7 @@
   
   __This is currently a draft, and has no official status.__
   
  -This document describes the roles (including Sponsor, Contributor, Shepherd) 
and provides an overview of the responsibilities of the different parties 
involved in an incubation process.
  +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.
   
   !!Incubator Project Management Committee (PMC)
   
  @@ -13,8 +13,8 @@
   * acceptance and oversight of candidate projects submitted or proposed to 
become part of the Foundation;
   * providing guidance and ensuring that sub-projects under it's purview 
develop products according to the Foundation's philosophy and guidelines for 
collaborative development;
   * providing a repository for the storage of incubation history and 
information;
  -* assisting a Podling's Shepherd in discharging her/his duties;
  -* regularly evaluating projects under its purview for the purposes of 
recommending to the Sponsoring Entity whether the project should:
  +* assisting a Podling's Mentor in discharging her/his duties;
  +* regularly evaluating projects under its purview for the purposes of 
recommending to the Sponsor whether the project should:
   ** successfully exit incubation;
   ** continue to receive guidance and support within the Incubator; or
   ** be terminated.
  @@ -23,7 +23,7 @@
   
   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.
   
  -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 Shepherd 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 Shepherd needs additional 
assistance, the Incubator PMC may choose to provide an experienced Shepherd to 
assist the main Shepherd in discharging their duty.
  +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.
   
   !!Chair of the Incubator PMC
   
  @@ -33,48 +33,48 @@
   
   A Candidate is a project that is proposed for incubation. A Candidate shall 
meet the following minimum criteria:
   
  -* affiliated with a named *Sponsor* (an ASF Member or Officer; see below)
  +* affiliated with a named *Champion* (an ASF Member or Officer; see below)
   
   Optionally, a candidate may:
   
  -* declare an affiliation with an existing Apache Project in which case it is 
expected that the Sponsor is a member of the affiliated project, and the 
project will become the *Sponsoring Entity*;
  +* declare an affiliation with an existing Apache Project in which case it is 
expected that the Champion is a member of the affiliated project, and the 
project will become the *Sponsor*;
   * specify requirements that may be anticipated during incubation; and/or
   * provide a summary of the project relationship/dependencies (existing or 
planned with existing Apache Projects/Products).
   
   Naturally, projects will need more than this in order to exit incubation 
status.
   
  -A candidate project compliant with the above criteria may be proposed by the 
Sponsor to the Sponsoring Entity for acceptance as a Podling.  Acceptance of a 
candidate shall be subject to the formal voting method of the Sponsoring 
Entity.  Should that vote be accepted, the Sponsoring Entity will request that 
the Incubator PMC accept the candidate as a Podling under incubation.  The 
Sponsoring Entity shall assign a Shepard, who shall be granted membership of 
the Incubator PMC for the duration of the incubation process.
  +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.
   
  -!!Sponsor
  +!!Champion
   
  -A candidate project shall be sponsored by an [Officer 
|http://www.apache.org/foundation/index.html] or [Member 
|http://www.apache.org/foundation/members.html] of the Foundation.  The Sponsor 
assists the candidate on their initial submission to a Sponsoring Entity.  
While private conversations are not generally encouraged within the Apache 
community, the Sponsor'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. 
  +A candidate project shall be sponsored by an [Officer 
|http://www.apache.org/foundation/index.html] or [Member 
|http://www.apache.org/foundation/members.html] 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. 
   
  -Where the Sponsor is not a Member of the Foundation (i.e. is an Officer 
only), the Sponsor shall be a member of the PMC of the Sponsoring Entity.
  +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.
   
  -While the Sponsor has no formal responsibility within the Incubation process 
(other than to review and comment on a Candidate's proposal within the 
Sponsoring Entity), it is expected that they will play an active role.  A lack 
of interest on the part of a Sponsor may be seen by the Incubator PMC as a 
negative indicator during the course of incubation.
  +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.
   
  -!!Sponsoring Entity
  +!!Sponsor
   
  -The Sponsoring Entity 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.
  +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.
   
  -A Sponsoring Entity will be one of:
  +A Sponsor will be one of:
   
   * The Board of the Apache Software Foundation.  In this case, it is expected 
that the candidate would become a TLP on successful completion of Incubation.
   * A Top Level Project within the ASF.  In this case, the project in question 
has agreed that the candidate is a good fit for their project, and will take on 
the candidate as a sub-project upon successful completion of Incubation.
   * 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.
   
  -Note that a Sponsoring Entity is more than just a final resting place for a 
candidate that successfully completes incubation.  The Sponsoring Entity, 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 Sponsoring Entity 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.
  +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.
   
  -However, while the Sponsoring Entity is expected to be actively involved, it 
is formally representated by the Shepherd.  The Shepherd is the individual 
accountable to the Incubator PMC for ensuring the incubation process is 
correctly followed.  In cases where the Shepherd is not fulfilling their 
responsibilities, the Sponsoring Entity (in particular its Chair) will be 
expected to remedy the situation.
  +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.
   
  -!Responsibilities of the Sponsoring Entity
  +!Responsibilities of the Sponsor
   
   * to provide initial approval for a Canidate to be accepted as a Podling
  -* to nominate a Shepherd for the incubation process
  +* to nominate a Mentor for the incubation process
   
  -!!Shepherd
  +!!Mentor
   
  -A Shepherd is a role undertaken by a permanent member of the Apache Software 
Foundation and is chosen by the Sponsoring Entity to actively lead in the 
discharge of their duties (listed above).  Upon acceptance by the Incubator 
PMC, the Shepherd automatically becomes a member of the Incubator PMC.  A 
Shepherd has specific responsibilities towards the Incubator PMC, the 
Sponsoring Entity and towards the members of the assigned Podling.
  +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.
   
   !Responsibilities towards Podling Members
   
  @@ -90,19 +90,19 @@
   * monitoring the Podling through the incubation process;
   * evaluating the compliance of the Podling with Incubator PMC policies and 
procedures; 
   * assessment of the Podling status with respect to continuation/exit 
strategy;
  -* to notify the Incubator PMC and Sponsoring Entity of the completion of 
administrative actions; and
  -* to provide updates to the Incubator PMC and Sponsoring Entity on the 
status of license grants (where and as appropriate) and other relevant legal 
information pertaining to the Podling.
  +* to notify the Incubator PMC and Sponsor of the completion of 
administrative actions; and
  +* 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.
   
   !Committers
   
  -The candidate shall declare an initial set of committers.  On acceptance of 
a candidate project, the assigned Shepherd shall be given access to the 
Podling's cvs repository for the duration of the incubation process.  This is 
to allow the Shepherd 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 Shepherd must earn them as 
would any other potential new committer.  In some cases, the Shepherd may be 
part of the initial set of declared committers, but this is not a requirement 
of the Incubation process.
  +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.
   
  -In association with its Shepherd and Sponsor, a Podling community is largely 
free to get on with the stuff they want to do (code, architecture, product, 
solutions, etc.) with minimal disruption related to the incubator process.
  +In association with its Mentor and Champion, a Podling community is largely 
free to get on with the stuff they want to do (code, architecture, product, 
solutions, etc.) with minimal disruption related to the incubator process.
   
   However, you need to make sure of a number of things:
   
  -* keep your Shepherd informed - he/she is reporting to the PMC and generally 
speaking "no news is bad news".  Of course, conducting business on the 
project's mailing lists is one important way to do this.  
  -* make sure your Sponsor is continuously in-the-loop and has the latest and 
greatest information about your project
  +* keep your Mentor informed - he/she is reporting to the PMC and generally 
speaking "no news is bad news".  Of course, conducting business on the 
project's mailing lists is one important way to do this.  
  +* make sure your Champion is continuously in-the-loop and has the latest and 
greatest information about your project
   * actively seek and recruit committers to your project - preferably linking 
you with existing Apache communities
   * make sure your decision making process is visible and accountable
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to