Apache Way Elements by Category

Categories are used to classify the main Ways of Apache.

Affiliation

Who you work for or get paid by.

Branding

Users should know who is behind the project.

Code

Code is useful; community makes it better.

Collaboration

Getting good enough consensus is often better than voting.

Committer

Committers have write access to the repository.

Conduct

Apache projects follow a code of conduct in project spaces.

Consensus

Getting good enough consensus is often better than voting.

Diversity

Diverse communities survive the loss of a single employer.

Hats

Make clear which hat you’re wearing.

Individuals

Participation is by individuals, not organizations.

Licenses

The pragmatic Apache License is the universal donor.

Offlist

Bring everything offlist back to the list.

PMCs

PMCs are responsible for managing the whole project - not just the code.

Privacy

Even in open source, some legal and personnel issues are handled in private.

Releases

Following release policy ensures releases are acts of the organization, not the release manager personally.

Servers

Using our own infrastructure ensures we are masters of our own fate.

Votes

Healthy communities that can find consensus will vote only when required.