Community Standards

In the interest of fostering an open and welcoming environment, we as contributors and maintainers strive to make participation in our communities a pleasurable, harassment-free experience.

We also recognize that authentic human-to-human collaboration and collective maintenance of our repositories are key to keeping our development sustainable and resilient.

Participation Standards

Examples of behavior that contribute to creating a positive environment include:

• Using welcoming and inclusive language
• Being respectful of differing viewpoints and experiences
• Gracefully accepting constructive criticism
• Showing empathy towards community members and newcomers
• Helping and mediating in cases of upsets or conflict

Examples of behavior which we ask everybody to avoid include:

• The use of sexualized language or imagery and unwelcome sexual attention or advances
• Trolling, insulting/derogatory comments, and personal or political attacks
• Public or private harassment
• Publishing others’ private information, such as a physical or electronic address, without explicit permission

We recognize that sometimes people may have a bad day, or may be unaware of the impact of their behavior. When that happens, you may carefully remind them in public or private, whatever is more appropriate. Assume good faith; it’s more likely that participants are unaware than that they are intentionally trying to denigrate others or reduce the quality of discussion.

Collective Maintenance Standards

Our organizational repositories are collectively maintained, not individually owned. To avoid and mitigate single points of knowledge and control, we encourage everyone to find and educate other maintainers to share knowledge and maintenance responsibilities.

All contributions must be human-authored, and fully understood and maintained by the contributors through

• writing all pull request, issue descriptions, comments, documentation and commit messages by hand,

• performing extensive self-review and taking full responsibility for submissions,

• caring for clarity and minimalism to ease the job of reviewers who accept changes into collective maintenance,

• avoiding the introduction of any runtime or development dependencies on LLM machinery.

If LLMs were used in any substantial way, contributors are invited to write in their own words how they made use of them. Automated “assisted/co-authored-by” trailers naming generative tools or models are discouraged as they do not properly disclose how those tools were used and provide free advertisement for a toxic billionaire-dominated industry.

In specific cases, maintainers may agree to configure bots (such as “dependabot”) to automatically generate pull requests. However, these changes must never be automatically merged and always require strict human review before merging.

Maintainers and Responsibilities

Project maintainers are those with commit rights to collective repositories or administrative rights to community communication channels. Each maintainer is asked to take responsibility and appropriate, careful action in response to witnessed instances of questionable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with our standards or do not match current project plans. They may also ban temporarily or permanently a contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

Our Community Standards apply to project repositories, communication channels, and gatherings, as well as to public spaces, when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via a social media account associated with the project, or acting as a representative at an online or offline event.

Reporting and Responses

If you experience or witness abusive, harassing, or otherwise unacceptable behavior you can talk to select project maintainers, currently Nami and Xenia. They will review reports and involve other maintainers as appropriate, and will respond in a way that is deemed necessary and appropriate to the circumstances, but not against your will.

Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident. Maintainers are themselves not exempt from being reported about and may face temporary or permanent repercussions as determined by other maintainers.

Attribution

Our Community Standards document is adapted from the Contributor Covenant, version 1.4, available at https://contributor-covenant.org/version/1/4, with additional sections and a focus on “collective maintenance” and “human authoring” added in September 2026.