Categories are used to classify the main Ways of Apache.
Who you work for or get paid by.
Users should know who is behind the project.
Code is useful; community makes it better.
Getting good enough consensus is often better than voting.
Committers have write access to the repository.
Apache projects follow a code of conduct in project spaces.
Diverse communities survive the loss of a single employer.
Make clear which hat you’re wearing.
Participation is by individuals, not organizations.
The pragmatic Apache License is the universal donor.
Bring everything offlist back to the list.
PMCs are responsible for managing the whole project - not just the code.
Even in open source, some legal and personnel issues are handled in private.
Following release policy ensures releases are acts of the organization, not the release manager personally.
Using our own infrastructure ensures we are masters of our own fate.
Healthy communities that can find consensus will vote only when required.