incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodent of Unusual Size <Ken.C...@Golux.Com>
Subject [STATUS] (incubator) Wed Dec 29 23:45:09 EST 2004
Date Thu, 30 Dec 2004 04:45:09 GMT
APACHE INCUBATOR PROJECT STATUS:                          -*-indented-text-*-
Last modified at [$Date: 2003/11/11 00:01:00 $]

Web site:  http://Incubator.Apache.Org/
Wiki page: http://Nagoya.Apache.Org/wiki/apachewiki.cgi?ApacheIncubatorProjectPages

[note: the Web site is the 'official' documentation; the wiki pages
 are for collaborative development, including stuff destined for the
 Web site.]

Pending Issues

    o We need to be very very clear about what it takes to be accepted
      into the incubator.  It should be a very low bar to leap, possibly
      not much more than 'no problematic code' and the existence of a
      healthy community (we don't want to become a dumping ground).

    o We need to be very very clear about what it takes for a podling
      to graduate from the incubator.  The basic requirements obviously
      include: has a home, either as part of another ASF project or as
      a new top-level project of its own; needs to be a credit to the
      ASF and function well in the ASF framework; ...

    o Moving the bylaw documentation from the Wiki to the main site
    o Merge the README.txt info on site management and the info on the
      "How to Participate" page into a single place
    o fix formatting of the project status pages

Resolved Issues

    o The policy documentation does not need ratification of changes
      if there seems consensus. Accordingly, the draft status of these
      documents can be removed and we will use the lazy "commit first,
      discuss later" mode common across the ASF for documentation

    o Coming up with a set of bylaws for the project

    o All projects under incubation must use a STATUS file (or a
      status.xml file if the project prefers XML) that contains
      information the PMC needs about the project. This file must
      live at the root of the project cvs module

    o Projects under incubation should display appropriate "disclaimers"
      so that it is clear that they are, indeed, under incubation

The Incubation Process

This tries to list all the actions items that must be complete for a project
before it can graduate from the incubator. It is probably incomplete.

Identify the project to be incubated:

  -- Make sure that the requested project name does not already exist
     and check to be sure that the name is not
     already trademarked for an existing software product.

  -- If request from an existing Apache project to adopt an external
     package, then ask the Apache project for the cvs module and mail
     address names.

  -- If request from outside Apache to enter an existing Apache project,
     then post a message to that project for them to decide on acceptance.

  -- If request from anywhere to become a stand-alone PMC, then assess
     the fit with the ASF, and create the lists and modules under the
     incubator address/module names if accepted.

Interim responsibility:

  -- Who has been identified as the mentor for the incubation?

  -- Are they tracking progress in the file



  -- Have the papers that transfer rights to the ASF been received?
     It is only necessary to transfer rights for the package, the
     core code, and any new code produced by the project.

  -- Have the files been updated to reflect the new ASF copyright?

Verify distribution rights:

  -- For all code included with the distribution that is not under the
     Apache license, do we have the right to combine with Apache-licensed
     code and redistribute?

  -- Is all source code distributed by the project covered by one or more
     of the following approved licenses:  Apache, BSD, Artistic, MIT/X,
     MIT/W3C, MPL 1.1, or something with essentially the same terms?

Establish a list of active committers:

  -- Are all active committers in the STATUS file?

  -- Do they have accounts on

  -- Have they submitted a contributors agreement?


  -- CVS modules created and committers added to avail file?

  -- Mailing lists set up and archived?

  -- Problem tracking system (Bugzilla)?

  -- Has the project migrated to our infrastructure?

Collaborative Development:

  -- Have all of the active long-term volunteers been identified
     and acknowledged as committers on the project?

  -- Are there three or more independent committers?

     [The legal definition of independent is long and boring, but basically
      it means that there is no binding relationship between the individuals,
      such as a shared employer, that is capable of overriding their free
      will as individuals, directly or indirectly.]

  -- Are project decisions being made in public by the committers?

  -- Are the decision-making guidelines published and agreed to by
     all of the committers?

Organizational acceptance of responsibility for the project:

  -- If graduating to an existing PMC, has the PMC voted to accept it?

  -- If graduating to a new PMC, has the board voted to accept it?

Incubator sign-off:

  -- Has the Incubator decided that the project has accomplished all
     of the above tasks?

Incubator Project


    o IRC channel #apache-incubator on
      (traffic is SUPPOSED to be logged to
      <URL:http://Source-Zone.Org/apache-irc/> so that
      the content of interactive discussions is available
      to everyone, but the logger isn't working)

    o Mailing lists:
      - (send to

      - (only for private communication)
        No project decisions will be made on the PMC list.

    o This status file is mailed to
      every Wednesday

Project committers (as of 2003-10-27):

    Note that the most current information is always in the CVS
    avail file, and can be found using:

        cat /home/cvs/CVSROOT/avail | grep incubator


    The Incubator Project doesn't do "releases" itself. Track of
    releases made by projects in the incubator is kept in the
    per-project status files.

Possible topics for educational documents:

    o A document which describes the 'ideal' way a project has to
      go to be successfully integrated into the ASF: the flow of the
      normal incubation process should be pictured
    o Glossary of important ASF terms and phrases
      (this was considered as very helpful on the reorg@ list)
    o Compact, but also encyclopedic link-directory which points
      to important info on the other ASF sites (e.g. to the Jakarta
      Charter or to the HTTPd dev pages)
    o General License-/Licensing documentation (ASL1.1, ASL2.2,
      TCK, JSPA)

# Local Variables:
# mode: indented-text
# tab-width: 4
# indent-tabs-mode: nil
# tab-stop-list: (4 6 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80)
# End:

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

View raw message