Our Pledge¶

We, as participants in the Apache Software Foundation, including contributors, committers, Project Management Committee (PMC) members, ASF Members, and officers, pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards¶

Examples of behavior that contributes to a positive environment for our community include:

• Demonstrating empathy and kindness toward others
• Being respectful of differing opinions, viewpoints, and experiences
• Giving and gracefully accepting constructive feedback
• Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
• Focusing on what is best not just for us as individuals, but for the ASF and the overall community

Examples of unacceptable behavior include:

• The use of sexualized language or imagery, and unwelcome sexual attention or advances
• Trolling, insulting or derogatory comments, and personal or political attacks
• Public or private harassment
• Publishing others' private information (such as a physical or email address) without explicit permission
• Other conduct which could reasonably be considered inappropriate in a professional or open source setting

Enforcement Responsibilities¶

Each ASF Project Management Committee (PMC) is responsible for clarifying and enforcing standards of acceptable behavior within their community, and may take appropriate and fair corrective action in response to any behavior that is inconsistent with this Code of Conduct.

PMC members have the right and responsibility to remove or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and to communicate reasons for their decisions when appropriate.

For matters that go beyond the scope of a single project or raise Foundation-wide concerns, the ASF President (or their designee) may investigate and take appropriate action, or escalate to the ASF Board or an ASF Officer if necessary.

Recusal¶

To preserve fairness and avoid conflicts of interest, any PMC member, ASF officer, or Member who is directly involved in or personally connected to a reported incident must recuse themselves from participating in the review, decision-making, or enforcement process. This includes cases where the individual is a party to the report, has a close personal or professional relationship with one of the parties, or may otherwise be perceived as lacking impartiality. In such circumstances, responsibility for handling the report should be delegated to uninvolved PMC members or escalated as appropriate.

Scope¶

This Code of Conduct applies to all ASF projects, mailing lists, source code repositories, issue trackers, events, chat services and community spaces, whether official or unofficial, and also applies when individuals are representing ASF or its projects in public spaces. Representation may include using an official ASF email address, posting via an official project or Foundation social media account, or serving as a delegate at an online or offline event. It also applies to ASF-wide channels, including the members@apache.org mailing list, ASF chat services, and other internal platforms.

Reporting Guidelines¶

While all participants should adhere to this Code of Conduct, we recognize that people may have a bad day or be unaware of the guidelines. When that happens, you may respond by pointing out the Code of Conduct. This can be done in public or private, as appropriate, but all responses should themselves remain respectful and constructive.

Assume good faith: it's more likely someone is unaware of how their behavior was received than intentionally trying to be harmful.

For issues that are specific to a single ASF project, reports may be directed to that project's Project Management Committee (PMC), typically via its private mailing list (e.g., private@project.apache.org).

If you are unable to resolve the situation, or feel unsafe or uncomfortable addressing it, you may report compliance issues in confidence to:

• President of The Apache Software Foundation (president@apache.org)
• Executive Vice President of The Apache Software Foundation
• Or one of the ASF's designated volunteers

The President (or a designated officer) may refer a report to the relevant PMC if the issue is project-specific, or handle it directly in Foundation-wide cases. Privacy and discretion will be respected in all cases.

If the concern is about inappropriate content in documentation or code (e.g., inappropriate language), please report it privately to the project's private mailing list (e.g., private@project.apache.org). If you have the necessary access, consider resolving or removing the concerning material with sensitivity to the perspective of the reporter.

Enforcement Process¶

When a Code of Conduct concern is raised, ASF officers or PMCs will assess the issue and determine the appropriate response using the following guidelines.

Note on Frivolous or Malicious Complaints The ASF values and encourages good-faith reporting of concerns. While most reports are raised constructively, knowingly filing false or malicious complaints, or repeatedly misusing the reporting process, may itself be treated as a violation of this Code of Conduct.

1. No Action Community Impact: Concerns raised do not represent a violation or do not rise to the level of requiring intervention. Consequence: No formal correction steps; may include an informational clarification for awareness.

2. Correction Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. Consequence: A private, written warning, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

3. Warning Community Impact: A violation through a single incident or series of actions. Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding community spaces and external channels like social media. Violating these terms may lead to a temporary or permanent ban.

4. Temporary Ban Community Impact: A serious violation of community standards, including sustained inappropriate behavior. Consequence: A temporary ban from any public interaction with the community. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may result in a permanent ban.

5. Permanent Ban Community Impact: A pattern of violating community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. Consequence: A permanent ban from any form of public interaction within the community.

In the case of ASF Members, any such action must be consistent with ASF Bylaw 4.7, which requires a vote of the Membership to terminate ASF membership. A PMC or ASF Officer may recommend a temporary exclusion from specific channels or events pending that process.

Attribution¶

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.