incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject cvs commit: incubator/site/incubation Process_Description.cwiki
Date Fri, 10 Sep 2004 10:05:44 GMT
crossley    2004/09/10 03:05:44

  Modified:    site/incubation Process_Description.cwiki
  Log:
  Minor text tweaks. Looks like big diff, because each paragraph is on one line.
  
  Revision  Changes    Path
  1.6       +5 -5      incubator/site/incubation/Process_Description.cwiki
  
  Index: Process_Description.cwiki
  ===================================================================
  RCS file: /home/cvs/incubator/site/incubation/Process_Description.cwiki,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- Process_Description.cwiki	1 Dec 2003 08:50:07 -0000	1.5
  +++ Process_Description.cwiki	10 Sep 2004 10:05:44 -0000	1.6
  @@ -14,7 +14,7 @@
   
   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 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.
  +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 your proposal - however, if you feel that your candidate project is not being addressed,
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.
   
   !! Acceptance
   
  @@ -22,7 +22,7 @@
   
   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 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.   
  +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 the PMC
and the Sponsor about 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 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.  
   
  @@ -46,13 +46,13 @@
   
   !!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 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.
  +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 cite. 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 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 your 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 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
board@apache.org 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. In other words, 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
board@apache.org 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. In other words, for a TLP objective the Incubator PMC okay 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.
   
  
  
  

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


Mime
View raw message