APACHE INCUBATOR PROJECT STATUS: -*-indented-text-*-
Last modified at [$Date: 2006-02-05 04:40:19 -0500 (Sun, 05 Feb 2006) $]
Web site: http://Incubator.Apache.Org/
Wiki page: http://wiki.apache.org/incubator/
[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; ...
See also:
https://issues.apache.org/jira/browse/INCUBATOR
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
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=517190)
o Coming up with a set of bylaws for the project
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=517190)
o All projects under incubation must maintain a status Web page that
contains information the PMC needs about the project.
(http://incubator.apache.org/guides/website.html)
o Projects under incubation should display appropriate disclaimers
so that it is clear that they are, indeed, under incubation
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=504543)
o Clearly and authoritatively document how to edit, generate,
and update the Web site (three separate functions)
(http://incubator.apache.org/guides/website.html).
The Incubation Process
==
TODO: this does not belong in the STATUS file and probably was integrated into
other documentation a while ago. That should be double-checked and then this
section should be removed.
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 www.nameprotect.com 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 on the project status Web page?
Copyright:
-- 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 listed in the project status file?
-- Do they have accounts on cvs.apache.org?
-- Have they submitted a contributors agreement?
Infrastructure:
-- 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
