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
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 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 maintain a status Web page that
contains information the PMC needs about the project.
o Projects under incubation should display appropriate "disclaimers"
so that it is clear that they are, indeed, under incubation
o Clearly and authoritatively document how to edit, generate,
and update the Web site (three separate functions)
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
-- 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.
-- Who has been identified as the mentor for the incubation?
-- Are they tracking progress on the "project status" Web page?
-- 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?
-- 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?
-- 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?
-- Has the Incubator decided that the project has accomplished all
of the above tasks?
o IRC channel #apache-incubator on irc.freenode.net
(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)
Please do not use the IRC channel for important stuff.
Important stuff should be on mailing lists.
o Mailing lists:
- [hidden email] (send to
- [hidden email] (only for private communication)
No project decisions will be made on the PMC list.
o This status file is mailed to [hidden email]
Committers / PMC members:
The most current information is always in the SVN
authorization file, and can be found using:
svn cat \
The authortive source is in the committers SVN module and can be
svn cat https://svn.apache.org/repos/private/committers/board/committee-info.txt | grep -A 100 '^\* Incubator'
These two lists should roughly be in sync, however, since this
synchronization tends to happen manually, that's not always the
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:
Note it has since been discussed and decided that a lot of content like this
should not be on the incubator website, but rather be part of "top-level"
documentation on the /foundation/, /legal/, /dev/ parts of www.apache.org.
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,
# 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)
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
|Free forum by Nabble||Edit this page|