incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: incubator/site/incubation Incubation_Policy.cwiki
Date Tue, 18 Nov 2003 11:09:59 GMT
nicolaken    2003/11/18 03:09:59

  Modified:    site/incubation Incubation_Policy.cwiki
  Commit the changes about how podlings publish the website.
  Revision  Changes    Path
  1.4       +30 -27    incubator/site/incubation/Incubation_Policy.cwiki
  Index: Incubation_Policy.cwiki
  RCS file: /home/cvs/incubator/site/incubation/Incubation_Policy.cwiki,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- Incubation_Policy.cwiki	14 Nov 2003 09:20:54 -0000	1.3
  +++ Incubation_Policy.cwiki	18 Nov 2003 11:09:59 -0000	1.4
  @@ -1,5 +1,4 @@
   In October 2002 the Board of Directors of the Apache Software Foundation passed a resolution
creating the Apache Incubator PMC (referred to as the "Incubator PMC" in this document) charged
with "accepting new products into the Foundation, providing guidance and support to help each
new product engender their own collaborative community, educating new developers in the philosophy
and guidelines for collaborative development as defined by the members of the Foundation,
and proposing to the board the promotion of such products to independent PMC status once their
community has reached maturity" [site:about/whatwedo|(reference Board Resolution)].
   The Incubator was tasked with the following responsibilities [site:about/whatwedo|(reference
Board Resolution)] :
  @@ -8,9 +7,7 @@
   * providing guidance and ensuring that subprojects under its purview develop products according
to the Foundation's philosophy and guidelines for collaborative development; and
   * regularly evaluating products under its purview and making the determination in each
case of whether the product should be abandoned, continue to receive guidance and support,
or proposed to the board for promotion to full project status as part of an existing or new
Foundation PMC; and be it further.
   !!About this Document
   This document is the normative reference for the policies and procedures put in place by
the Incubator PMC for the Incubation process, which is used by the Incubator PMC to discharge
their duties as described above.
   It contains the minimum requirements that all new products and projects must meet before
they will be fully accepted into the Apache Software Foundation.
  @@ -18,30 +15,24 @@
   The document makes use of the terms MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY and OPTIONAL.  Where capitalised, these terms are to be used
as per the definitions found in [RFC 2119|].
   This document contains the minimum requirements and processes that must be met by products
and projects wishing to become part of the Apache Software Foundation.
   This document does not apply outside the process of Incubation.  Policies and processes
that need to be met by products under incubation are not mandated (by this document) for other
projects and sub-projects within the ASF.
   !Relationship to Other Documents
   This document is the normative set of requirements for Incubation.  Where other documents
are in conflict, this document should be taken as correct.
   !! Changing this Document
   The contents of this document are formally approved by the Incubator PMC.  All changes
must be authorised by the Incubator PMC.
   !!Objectives of the Process
   To provide a clear path for potential projects and sub-projects within the ASF to move
from proposal stage through to fully membership in such as way as to ensure :
   * new projects and sub-projects are developing products according to the ASF's philophy
and guidelines for collaborative development;
   * the ownership of any code initially submitted by the project is formally and legaly transferred
to the ASF; and
   * only those products that meet the Apache's requirements are fully accepted into the ASF.
   !!Overview of the Process
   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.
  @@ -60,18 +51,15 @@
   !!!Entry to Incubation
   Entry to Incubation requires a number of hurdles be passed.
   !! Proposal
   In order to enter the Incubator, a Candidate MUST 
   * be nominated for incubation by a member of the Apache Software Foundation ("The Champion");
   * be approved by a Sponsor.  
   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.
  @@ -81,7 +69,6 @@
   __Need to provide a short list__
   !!Acceptance of Proposal by Sponsor
   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 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
  @@ -94,19 +81,15 @@
   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.
   !!Creation of Podling
   Upon acceptance by the Incubator PMC, the Candidate becomes a Podling under the care of
the Incubator PMC.  
   Upon acceptance by the Incubator PMC, the Podling's Mentor becomes a member of the Incubator
PMC (should they not already be one).
   !!!Incubation Activities
   The following sections detail the minimum activities that must be undertaken by the various
parties during an Incuabation process.
   !!Setting Up a New Podling
   Once the Podling and Mentor have been accepted by the Incubator PMC, the following activities
SHOULD take place :
   * creation of lists;
  @@ -115,7 +98,6 @@
   * Incubator PMC mandating a helper Mentor
   !!Ongoing Activities
   The progress of a Podling SHALL be tracked in a STATUS file.  The STATUS file SHALL be
stored in the ''incubator'' module in the ASF CVS repository.
   The STATUS file SHALL include the following minimum content :
  @@ -125,7 +107,6 @@
   * status of Podling against exit criteria.
   The Mentor MUST ensure that the STATUS file is up to date at all times.
   !!Review of Activity
   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.
  @@ -141,7 +122,6 @@
   Termination and Escalation are discussed in more detail in section "Exitting the Incubator".
   !!Disputing an Assessment
   If the Podling or Mentor disagree with an assessment, they MAY request the Incubator PMC
review the report.  Such a request MUST include a details of what the Podling and/or Mentor
is disputing, and their reasons for doing so.
   Upon receipt of an Assessment Dispute, the Incubator PMC SHALL review the request and provide
feedback to the Podling and Mentor.  Such feedback MAY include a change to the original Assessment.
  @@ -162,28 +142,23 @@
   The decision of the Board of the Apache Software Foundation is final.
   A recommendation by the Incubator PMC for continuation of incubation SHALL include development
recommendations. The Incubator PMC SHALL ensure that the recommended actions are tangible
and quantifiable.  
   The Mentor SHALL review the contents of the continuation recommendation and ensure that
the development recommendations are carried out over the following review period.
   !!!Podling Constraints
   While in Incubation, Podlings are constrained in the actions they can undertake.
   Podlings are, by definition, not yet fully accepted as part of the Apache Software Foundation.
 Podling web sites MUST include a clear disclaimer on their website and in all documentation
stating that they are in incubation.
   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 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.
   As podlings are not yet fully accepted as part of the Apache Software Foundation, any software
releases (including code held in publically available CVS) made by Podlings will not be endorsed
by the ASF.
   However, as software releases are an important part of any software project, they are permitted
in certain circumstances, as follows.
  @@ -197,10 +172,38 @@
   * the release archive MUST contain the word "incubating" in the filename; and
   * the release archive MUST contain an Incubation disclaimer (as described in the previous
section), clearly visible in the main documentation or README file.
   !!Use of Apache Resources
  -__Is this required?__
  +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.
  +! Website
  +* every project site sources stay in the project CVS
  +* every project has this URL space where to publish the site:
  +* every project has an incubation status file under
  +* every project has eventual extra incubation docs under:
  +* The website is live in directory on
  +{{{         /www/
  +{{/www/}} has to be checked out of CVS.  We don't care
how it gets into CVS, or which CVS module it lives in, but it had better be there.
  +People using Maven, ForrestBot, or any other tool still have to address the CVS publishing
requirement that the infrastructure team has laid out.  If that is done, then we just run
cvs up in that directory to load the site from CVS.
  +The Mentors MUST add the information about the CVS module and dir where the published site
is, in the project incubation status file.
  +If the project does not want to host the published site in their CVS, it has a space under:
  +{{{        incubator-site/build/site/projectname/**
  +The site is automatically updated from there once a day.
   !!!Exitting the Incubator

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message