Developer Information

• How the ASF Works (See also Contact Apache FAQ and ASF FAQ)
• Introduction for contributors
• Tips for email contributors
• Guide for new committers
• Committers FAQ
• Publish private website

All requests for Infrastructure assistance need to be sure that the relevant project PMC is involved. In fact the PMCs can handle many Infrastructure items for themselves.

• Procedures for creating an ASF Top-Level Project
• Procedures for creating an ASF Project (where the PMC already exists)
• PMC FAQ
• Make a new committer account request
• Make a karma request
• How to report issues and request project resources
• Duties of the PMC Chairs
• Legal stuff
• Manage your project website
• Choosing names for ASF projects and products

• About the Apache Licence
• Licence FAQ
• Legal Policies, Forms, and Information for Apache Committers
• ASF Source Header and Copyright Notice Policy
• Applying the Apache License, Version 2.0 (some parts of this are superceded)
• ASF Trademark And Logo Guidelines

• Info on managing your project website

• Project Mirroring Guidelines
• How-to publish a mirrored release
• Hands-down mirror guide by Stefan Bodewig
• Releases FAQ
• Repository FAQ
• Release signing
• How To Use GnuPG For Key Management At Apache
• How To Avoid SHA-1
• How To Generate A Strong Key
• How To Transition To A Longer Key
• Release publishing
• Dynamic release download pages
• Releases from incubating projects

Each project uses their own issue tracker. There is no standard, so visit each project website to find which one they use.

• See notes about expectations, subscription instructions, nettiquette, etc. for all mailing lists. See Public Forum Archive Policy.
• Each project has their own project mailing lists.
• There are some other non-project lists (e.g. legal-discuss@ and community@ and various announcement lists).
• Privacy notes about non-public lists and about balancing confidentiality and public discussion.
• Tips for email contributors
• Mailing list moderation