APACHE INCUBATOR PROJECT STATUS: -*-indented-text-*-
Last modified at [$Date: 2003/03/30 00:51:38 $]
The Incubation Process
==
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 shepherd for the incubation?
-- Are they tracking progress in the file
incubator/projects/{project_name}/STATUS
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 in the 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 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
=
Background:
o See the bottom of this file for the official resolution/
charter-as-it-stands
o IRC channel #apache-incubator on irc.openprojects.net
traffic is logged to http://Source-Zone.Org/apache-irc/>
so that the content of interactive discussions is available
to everyone
o Mailing lists:
- [EMAIL PROTECTED] (send to
[EMAIL PROTECTED])
- [EMAIL PROTECTED] (only for private communication)
No project decisions will be made on the PMC list.
o This status file is mailed to [EMAIL PROTECTED]
every Wednesday
Project committers (as of 2003-03-29):
o incubator-core:
aaron,coar,fielding,fitz,gstein,jim,nicolaken,striker
o incubator and incubator-site:
{incubator-core},acoliver,bloritsch,dion,glongman,hammant,hlship,
jefft,jvanzyl,leif,leosimons,medgar,mindbridge,nclayton,proyal,
rana_b,rlewisshell,vinayc
o incubator-altrmi:
{incubator-core},acoliver,hammant,vinayc,leif,jefft,proyal,bloritsch
o incubator-ftpserver:
{incubator-core},hammant,rana_b,jvanzyl
Release:
none yet; still ramping up
Resolved Issues:
none yet; still ramping up
Pending issues:
o Coming up with a set of bylaws for the project
o the Website. Use Forrest?
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 pag
