These pages provide a directory of technical details pertinent to all Apache projects, for developers, committers, release managers and PMC members contributing to any Apache project.
If you can't find information here, ask on your project's mailing list, or contact the Community Development project's mailing list for more general questions. There are many experienced ASF people who can help. We also have a sitemap summarizing all the pointers available.
Find information about tools and processes the ASF and its projects use to manage source code, mailing lists, and websites. You can also find how-to guides for committers and Project Management Committees (PMCs).
High-level notes on Apache Infrastructure
How to become an Infra Volunteer
Host and service status monitor. Infa has already been alerted if a service shows as down.
Machine/Host List of ASF servers
How the ASF Works (See also Contact Apache FAQ and ASF FAQ )
Guide for new project committers
General Committers FAQ
Crowd funding Community funding disclaimer
The project PMC must be involved in any requests for Infrastructure assistance. Remember that PMCs can handle many Infrastructure items for themselves.
Learn How To...
...read the PMC FAQ
Legal Policies, Forms, and Information for Apache Committers
Rationale of how to apply the Apache License, Version 2.0 (descriptive, not policy)
Apache Trademark Policy - for outside parties
Apache Project Branding Requirements - for projects
Using proper SVN eol-style
Overview of the ASF CMS for project websites. Note: no new projects can use the CMS, and Infra is helping existing projects migrate off the CMS to other options.
How to manage your project website
How to transition to a longer key
Each project uses their own issue tracker to track bugs, requests, and other action items - typically JIRA or BugZilla. Every Apache project decides how to track issues, so see each project website to find how they track issues.
Please read the Public Forum Archive Policy before posting on any Apache mailing list!
Subscription instructions and netiquette for all Apache mailing lists.
All Apache projects have their own set of project-specific mailing lists
There are some other non-project mailing lists (e.g. legal-discuss@ and community@ and various announcement lists).
Privacy notes about non-public lists and about balancing confidentiality and public discussion.
All Apache mailing lists are archived:
Apache provides a paste bin service for committers to use at https://paste.apache.org.
Anyone can view the pastes (except those marked 'committers only'), but only committers are allowed to paste new data on the site.
Infrastructure hosts the s.apache.org URL shortening service for our committers. When including URLs in PMC reports, please use this service and not other URL shorteners.
This is an overview of activity going on with various Apache projects. SVN commits, bug reports, tweets, you name it.
Available as of yesterday, more self serve features were added to the .asf.yaml toolset, based around Github Branch Protection.
You can now add the following features :-
The Infrastructure team is constantly looking for ways to do its work more quickly while maintaining the ASF standards of reliability, security, and almost-continuous availability. The more the team can...
Today, ASF Infra launched new features for projects wishing to update their notification schemes for git/github activity on their own.
Via the .asf.yaml file, projects can now define notification schemes...