See the general document Procedures for Creating a Top-Level Project. This document assumes
that the PMC/TLP infrastructure is already in place and is meant for when a new
codebase joins a PMC.
Of course there are some tasks that can only be done by the Infrastructure
team. Discuss the options on your dev|pmc mailing list first and be clear
about what you want to be done. Compile those into an email message and send
it to the infrastructure@apache.org mailing list. To help facilitate
your request, you are also requested to file an issue tracker request with this information.
The following is intended to be a standard form for helping to setup a
new project entering incubation or for a project moving to top-level.
It is an evolving document - please patch if you discover more.
Not all entries will be valid. For example, in almost all cases only
the -dev mailing list will be created during incubation. It would be
rare to also create a -users list for a new project.
You do not need to specify every detail. The infrastructure people already
know about many background things, e.g. DNS entries, unix groups, etc.
Prepare the following text by discussing with your developers. When you
have the necessary decisions, then use this template to send your request
to infrastructure@apache.org
Other tasks, such as Issue Tracker and Wiki, are separately described below.
-------------------------------- snip --------------------------------
The $TLP PMC has agreed to accept the $PROJECT project for incubation.
To aid in the process, would infrastructure please do the following:
#=======================================
[1] Mailing List (i) addresses
I. $PROJECT-dev@$TLP.apache.org
II. $PROJECT-users@$TLP.apache.org
III. $PROJECT-commits@$TLP.apache.org
(ii) remote moderators ...
Note: At least two, preferably world-wide coverage.
(iii) archives
mbox
I. http://$TLP.apache.org/mail/$PROJECT/dev/YYYYMM.gz
II. http://$TLP.apache.org/mail/$PROJECT/users/YYYYMM.gz
III. http://$TLP.apache.org/mail/$PROJECT/commits/YYYYMM.gz
(iv) options
I. Reply-To: Header [X] yes [ ] no
NOTE: $PROJECT-commits@$TLP.apache.org -> $PROJECT-dev@$TLP.apache.org
II. Message Trailer [ ] yes [X] no
#=======================================
[2] Source Tracker
(i) Subversion
The PMC chair can create the project namespace (svn mkdir) and modify the
asf-authorization file accordingly.
Just tell us about any special requirements - i.e. mailing lists configs.
#=======================================
[3] Initial Committer list
...
#=======================================
[4] Snapshots
Create directory http://people.apache.org/snapshots/$TLP
Tweak the script that creates the snapshots (~apmail/bin/taritup).
-------------------------------- snip --------------------------------
There are various things that your project can do to aid the establishment
of your project resources. If your project committers do not have the
permissions, then your PMC's ASF members would.
#=======================================
Wiki
If you want a Wiki, then see
http://wiki.apache.org/general/HowToMakeWikiAdminRequests
#=======================================
Issue Tracker
There is a choice between Jira and Bugzilla
(i) Bugzilla URL:
http://issues.apache.org/bugzilla/buglist.cgi?product=$PROJECT
Send email to infrastructure ...
Product description:
Components:
(ii) Jira
Follow the separate instructions at
http://wiki.apache.org/old/JIRA
per-separately releasable package
Project Name:
Project Lead:
Preferred Project Abbreviation(s):
A list of Jira accounts to mark as project developers
...
[if necessary, provision can be made to have admins list
different from developer list]
As an example, although Jakarta Commons is a single source code module in the source
repository, each project would be a separate Jira project, although sharing a common
permissions schema.
After the project is setup in Jira, the project's PMC will be responsible
for the configuration of its own settings: components, versions, etc.
#=======================================
Apache Project Listing
If you want your project included in the Apache Projects list at: http://projects.apache.org/
then you need to ensure that the TLP details are included in:
http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/pmc_list.xml
and
http://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/TLP.rdf
You can then create and submit the project DOAP as described in:
http://projects.apache.org/create.html
#=======================================
Apache Gump
If your project already uses Gump, then the move will mean that you need to
adjust your Gump descriptor in SVN.
#=======================================
Contents