An overview of how Apache projects work with ASF Infrastructure (Infra) services, support, and processes.

Purpose

ASF Infrastructure supports the technical operations of all Apache projects, maintaining the shared systems that enable collaboration and transparency across all Apache projects. This guide helps podlings and project members understand when and how to contact Infra, what services they provide, and where responsibilities lie between Infra and the project.

ASF Infrastructure Overview

ASF Infrastructure (Infra) manages and maintains:

• Git repositories and commit access
• Mailing lists and archives
• JIRA and GitHub integration
• Buildbot, Jenkins, and CI systems
• Website hosting and mirrors
• Authentication and identity systems (LDAP)
• dist.apache.org, and downloads.apache.org
• DNS and subdomain management
• Self-service tools for project management

ASF Infrastructure ensures that ASF-wide systems remain secure, reliable, and consistent for all projects. It maintains the shared technical foundation that enables Apache communities to collaborate, build, and release software independently.

Infra is operated by a small professional team supported by volunteers, reporting through ASF Operations to the ASF Board of Directors. This structure provides continuity, accountability, and long-term stability across all Foundation services.

ASF Culture and Infra

ASF Infrastructure operates under the same values that guide all Apache communities:

• Community over code: Infra supports collaboration, not individual preferences.
• Transparency: All work is conducted in public systems, allowing anyone to learn from past discussions.
• Meritocracy: Trusted volunteers and staff manage these systems; respect their time and expertise.
• Self-service and shared responsibility: Contributors are encouraged to use ASF tools to handle tasks themselves.

ASF Infrastructure is not corporate IT. it supports a global, volunteer foundation where transparency and shared responsibility take priority over speed.
Infra’s role is to enable communities to work autonomously, not to manage them.

The Infrastructure team includes both full-time staff and volunteer contributors who maintain the systems on which all ASF projects rely.

When to Contact ASF Infrastructure

Before contacting Infra, please check if your request can be handled through Self-Serve. Many everyday tasks can be completed directly by your PMC through the self-service portal — this is the fastest and preferred approach.

Common Tasks You Can Do Yourself

Use Self-Serve for:

• Creating or renaming Git repositories
• Setting up or redirecting project websites
• Creating mailing lists
• Managing DNS and subdomains
• Configuring Jenkins, Buildbot, or GitHub Actions integrations within ASF policy
• Adjusting LDAP group or committer access (via PMC tools)

Only PMC or PPMC members should use these tools, and changes should reflect agreed community decisions.

💡 Tip: Most routine project setup tasks can be completed in minutes through Self-Serve.

⚠️ Note on Security:
Report infrastructure-level vulnerabilities (e.g., affecting ASF servers, domains, or services) privately to the ASF Security Team.
Report project or code-level vulnerabilities through the project’s own security process or disclosure channel.
Do not open public Infra JIRA tickets for any security issue.

When to File an INFRA Ticket

Use the INFRA JIRA project when:

• A service is broken or unreachable (e.g., Jenkins, mail delivery, mirrors)
• A change is not available in Self-Serve
• You encounter a permissions or configuration issue you cannot fix
• You need assistance recovering or migrating ASF-hosted infrastructure
• You need help with Foundation-managed systems (e.g., LDAP, mirrors, or build clusters)

Infra may decline requests about third-party services not integrated with ASF systems. Infra does not handle project-level technical or governance issues.

Requests should come from the project’s PMC (or PPMC for podlings) after community agreement.
This ensures transparency and accountability.

How to Request Help

Check First

• infra.apache.org – main site
• status.apache.org – system health
• selfserve.apache.org – self-service portal

Be Patient and Professional

Infra triages tickets based on urgency. Infra aims to respond promptly but provides no fixed service-level guarantees. Response times vary with priority, workload, and volunteer availability. Do not assume silence means inactivity, all requests are tracked and reviewed.

All Infra requests are public and archived for traceability.
ASF systems are permanent records, so write professionally and thoughtfully, knowing your comments become part of ASF’s history.
Do not include passwords, private data, or confidential information from third parties in tickets.

Communication Channels

Do not contact Infra team members directly. All requests must go through tracked systems (JIRA, mailing lists, or Self-Serve).

Common Requests

Responsibilities

ASF Infrastructure handles

• System setup, uptime, backups, and security
• Global ASF policies for access control and compliance
• Centralized authentication (LDAP, GitHub)
• Core build and distribution services

Projects and podlings handle

• Code, documentation, and website content
• Build configurations and CI scripts (including GitHub Actions)
• Contributor onboarding (via PMC / roster tools)
• Initiating requests through Infra or Self-Serve tools
• Ensuring PMC consensus before making Infra requests
• Compliance with ASF policies, including Brand Management, Release Policy, and Security.
• Account management for committers via id.apache.org.

Note: Infra may occasionally end support for deprecated website systems (e.g., legacy CMS). Projects are responsible for migrating to the current supported build and deployment systems.

For Podlings in the Apache Incubator

Podlings should:

• Utilise ASF infrastructure early, including GitHub, mailing lists, and distribution mirrors, among others.
• Coordinate with mentors before filing Infra tickets if unsure.
• Follow ASF naming, branding, and release requirements.
• Use selfserve.apache.org for most setup tasks once established.

Mentors should help podlings learn ASF systems, but avoid filing tickets on their behalf unless necessary. Part of mentoring is teaching self-sufficiency.

Infra does not manage Incubator policy or mentor-related questions, those belong to the Incubator PMC.

Best Practices

• Check status.apache.org before opening a ticket.
• Use Self-Serve first, most requests can be handled there.
• Read Infra documentation before requesting help.
• Avoid “critical” priority unless truly blocking.
• Share what you learn with your community.
• Respect time zones and volunteer workloads.

Related Resources

• ASF Infrastructure Home
• INFRA JIRA Project
• ASF Self-Serve Portal
• ASF System Status Dashboard
• ASF Identity Management

ASF Cultural Takeaways

• Infra enables, communities own. Projects are responsible for their own success.
• Transparency is essential. Keep communication in public, tracked systems.
• Teach what you learn. Every solved ticket is a chance to document and share.
• PMC consensus first. Infra requests should reflect community decisions.
• Peer collaboration, not customer support. Infra is a shared service run with the community, not for it.
• Write thoughtfully. Infra systems are public and permanent records.

Key Takeaways

• Use selfserve.apache.org for routine requests and INFRA JIRA for complex ones.
• Check status.apache.org before reporting outages.
• Manage your ASF ID via id.apache.org.
• Never contact Infra members directly. Always use tracked systems.
• PMC-approved requests only. Confirm community agreement before filing.
• Be patient, polite, and transparent.

Working with ASF Infrastructure

Working effectively with ASF Infrastructure is part of practicing the Apache Way, open communication, shared responsibility, and respect for those who keep the Foundation running.