(Follow the Infra team via Twitter or read the team blog )

The ASF does not have offices or buildings, it's a virtual entity that exists only on the internet. Its only physical existence is the technical infrastructure that enables it to operate.

The ASF Infrastructure is primarily composed of the following services:

• the web serving environment (web sites and wikis)

• the code repositories

• the mail management environment

• the issue / bug tracking

• the distribution mirroring system

The Infrastructure team is responsible for the management and day-to-day system administration and operation of the various hardware that runs the above services. They are also responsible for approving the installation of a new system or software on the ASF machines.

The Infrastructure team deploys in production a number of Apache softwares, including HTTP Server (httpd), Subversion, SpamAssassin, Tomcat, Traffic Server, mod_perl, RAT (incubating), Gump and Continuum, mod_mbox, Pulse and Orthrus (see labs), Solr, Directory Studio, a selection of in-house projects, and the Apache CMS.

Below is a list of documentation on the services provided by Infrastructure:

Infrastructure details

• Twitter stream

• How to be an infrastructure volunteer

• How to report issues and request project resources

• Infrastructure mailing lists

• Solaris zone hosting and FreeBSD Jail hosting

• Build Services

• Request a new mailing list

• Request a mailing list configuration change

• SSH Access

• Configure e-mail forwarding

Machines and Services

• Machines List

• Services List

• Public Host and Service Status - ASF Infra has already been automatically alerted if a service is down. This page is for your comfort.

Websites

The site-dev mailing list manages the following websites:

• projects.apache.org - an index into all the Projects at the ASF

• www.apache.org - the main ASF website ( build instructions )

• people.apache.org - details about the individual committers at the ASF

Software distribution and mirroring

Bad mirrors are automatically removed from the rotation of "preferred" mirrors. If a mirror stays bad for more than a couple of weeks, it is usually removed permanently. So, there is no need to post helpful mail to infrastructure when a mirror is down.

• Become an ASF mirror

• Mirror Status

SVN

• SVN via the webserver

• SVN via ViewVC

• Version Control with Subversion - the book

• FAQs about Subversion at ASF

• Anonymous SVN

• Committer SVN access

• Make an SVN admin request

• Git access to Apache codebases

Issue tracking

Infrastructure uses JIRA for task management and issue tracking. To request changes to an issues tracking system (for example, to request that a project be added), see How to report issues and request project resources

Information on supported issue tracking systems:

• Bugzilla Manual

• Bug reporting guidelines

• Jira Manual

• ASF Jira FAQ

Wikis

• General wiki - however an effort is being made to bring all of that old information together on this www.apache.org website.

• Wiki FAQ