A committer is an individual who has write access to the codebase of an Apache project.
The main information resource for you in this role, apart from the wisdom of your project colleagues, is the New Committers Guide.
If you are not an Apache committer, but wish to become one, the instructions on how to contribute to Apache projects will be more useful to you.
The Apache Software Foundation periodically organizes conferences focusing on software developed at Apache and on the way that Apache develops its software. Learn about what's happening at Apache, hack code and meet the faces associated with the names!
A face-to-face or shared online gathering for hacking code together. Hackathons are generally held at ApacheCons, as well as at other times.
A face-to-face gathering for work on Apache infrastructure by our amazing infra contractors and volunteers.
Heed the warnings in these two email threads about what it means to be a committed person at the ASF and how to deal with the pressures that arise from such dedication:
We each need to re-read these important messages from time to time and remind ourselves and our communities of the need for self-care and care of others.
Contact the Incubator Project. They will assist you in starting a project or moving an existing one into the ASF.
Apache Labs could also be for you if you want to start something new.
Note: this is an incomplete collection and not authoritative.
As an Apache volunteer, you have the right to set your own priorities and do the work that scratches your own itch. As a Committer, you have a responsibility to the community to help create a product that will outlive the interest of any particular volunteer, including yourself. For example, he code that you commit should be clear enough that others not involved in its current development will be able to maintain and extend it. It also means that you are responsible for helping to grow and maintain the health of the Apache community.
More specific responsibilities of Committers include:
usersemail lists for the projects they work on and together provide prompt and useful responses to questions from users and their developer colleagues.
Committer status and merit never expire. If you become inactive for a time (usually six months or more), your account may be deactivated for security reasons. Most projects allow reactivation of committer status by application to the PMC.
Some projects use the concept of emeritus committer for those who have contributed to the project but can no longer can give much time to it.
For any substantial codebase that has been developed outside the ASF, there is a process to complete before the code can be committed. The Incubator team manages this. The first step is to contact your PMC.
Apache project business should almost always be on your public
dev@ mailing list, unless there is a specific reason to use
private@. See the discussion about private vs. public lists.
The most likely explanation is that the commit message is awaiting moderation. Messages will be delivered promptly without moderation once the moderator approves posts from your
You might notice something that needs changing, for example the configuration for a mailing list. The request to the
users@infra list or the
apmail@ alias needs to come from your Project Management Committee. That ensures that the requests are official, and not just an individual's desire.
There are many things that the PMC or PMC chair can do directly, thereby easing the load on the infrastructure team (Infra).
Infra uses the
email@example.com mailing list to discuss new infrastructure developments at the ASF. For service downtime announcements and current information on operations, we use Infrabot. For general announcements regarding services and the like, Infra has a blog.
Committers may access
home.apache.org. See the related information in the New committers' guide.
Note that you do only have sftp access. There is no shell access. RSA SSH keys are required for sftp access, which you can update via Whimsy or id.apache.org.
You can publish a small personal website in
public_html, as described in the New committers' guide. Never store secret/private keys (the private half of an SSH keypair, or a PGP private key) on any ASF machines.
Take any message about a change to the host key or any "Error validating server certificate" very seriously: it may indicate a man-in-the-middle attack is in progress. Do not ignore this message.
Before contacting the Apache infrastructure team, check that you are logging in to the correct machine, and verify the currently published SSH fingerprints for Apache hosts, as described under "Identity theft" in the New committers' guide.
Nexus uses LDAP-based authorization. If you have changed your LDAP password recently it is possible you have a cached version of your old password stored, perhaps in a
settings.xml file locally. Maven makes repeated attempts to try this authorization and within 10 seconds you might find your LDAP account locked as a result. Try accessing another LDAP-based service to test the theory.
The cure is to go to https://id.apache.org/reset/enter and reset your LDAP password to clear the locked account. Change any cached credentials locally and try staging to Nexus again.
The most common reason is that you've forgotten your password! The password you use for Subversion is the same as the password you use for access to LDAP
id.apache.org. You will not be prompted to enter it frequently. This makes it easy to forget.
Apache employs a number of different HTTP authentication realms. You will need to enter your password whenever you access a new realm. (Subversion prints information about the realm when you are prompted for the password.)
Of course, it is also possible that you're accessing a URL which is restricted. That's probably for a good reason, so unless you know that you should have access, don't bother the infrastructure team about being locked out.
If you do forget your password please visit
https://id.apache.org/ to reset it.
In Subversion, url:
Very rarely if ever. See the version control FAQ for more details.
See these instructions.
If it is a public list, email the
-subscribe address (such as
firstname.lastname@example.org) from the address you want subscribed, and
reply to the confirmation mail. For more information see the mailing list guide.
Private lists use the same procedure, but it's recommended to use the self-subscribe app. That avoids needing to wait for a human moderator to check and green-light your subscription request.
At the time of writing the self-subscribe app lets ASF Members subscribe to any ASF list and other
committers to subscribe to a few foundation-wide lists. Committers who wish to subscribe to other lists (such as a private@ list of their project)
should still email the
Committers can use Whimsy to check their details, including subscription information.
Information on list subscriptions is private, so is not available to all committers. Moderators can send an email to:
Anyone with access to the apmail account can run the following command to get a count of subscribers:
ezmlm-list ~apmail//lists/<var>project</var>/<var>listname</var>| wc -l
Remember that there often are people subscribed to the digest version of the list, too:
Your forwarding address(es) are stored in LDAP and maintained through the Self Serve app. Forwarding is done directly from LDAP.
This information has moved here
Note: While there is not an official list, the following principles have been cited as the core beliefs of The Apache Way:
A non-official The Apache Way website is available.
Yes, Apache projects must always be managed independently of undue commercial influence.
Yes, the software products Apache produce are always available to download and use at no cost.
Consult with the PMC of the product involved, and see How to submit a patch for project code
It depends on variables including staff workload. You shouldn't be worried until a week or two has passed since the date you expected the document to arrive.
When a CLA is submitted, there are several stages to the approval process.
private@list for a notice from
secretary@(this only happens if the ICLA mentioned which TLP to notify). Others will need to check the list of ICLAs. This is automatically generated, about once an hour, from the file maintained by the Secretary.
PMCs are responsible for managing their own Apache project brands, and committers are encouraged to assist. If you spot any potential misuse or infringement of Apache brands or trademarks by third parties, please follow our Apache Trademark Use Reporting Guidelines.