It contains information aimed at developers,
committers, release managers and pmc members.
If you cannot find your answers here, then please ask on your project
mailing lists. There are many experienced ASF people there to help.
The content is categorized below. Alternatively, this
sitemap summarizing all the information in
/dev/ is available.
Some further content starts its life
on the General Wiki, and may move to these pages as it
matures.
Here you can find information about tools and processes used by Apache projects and the ASF to manage our source code, our mailing lists, our websites, and also How-To guides for committers and Project Management Committees (PMCs).
Notes on Apache Infrastructure
How to become an Infra Volunteer
List of Services available to Apache projects
Contacting infra and requesting resources
Public Host and Service Status monitoring - ASF Infra has already been automatically 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
use of crowd funding Community funding disclaimer
All requests for Infrastructure assistance need to be sure that the relevant project PMC is involved. 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
Source Code Repositories - SVN and GIT
Using proper SVN eol-style
Overview of the ASF CMS for project websites
Reference Manual for working with ASF CMS
How to manage your project website
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.
Read about how paste.a.o works on the site or read this overview blog post.
This is an overview of activity going on with our projects. SVN commits, bug reports, tweets, you name it.
There will be a planned reboot of Jira on Friday 7th August at 00:00 UTC.
This is 72 hours notice as recommended in our Core Services planned downtime SLA.
Currently,...
As some of you are aware, there have been some issues syncing changes from repositories on https://git-wip-us.apache.org to the mirrors on GitHub.
The issues we are seeing:
