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
有助于创造积极环境的行为包括但不限于:
- 措辞友好且包容
- 尊重不同的观点和经验
- 耐心接受有益批评
- 与社区其他成员和新人友善相处
- 为麻烦与冲突提供帮助和调解
每个人都不应采取的行为包括但不限于:
- 发布与性有关的言论或图像、不受欢迎地献殷勤
- 捣乱/煽动/造谣行为、侮辱/贬损的评论、人身及政治攻击
- 公开或私下骚扰
- 未经明确授权便发布他人的资料,如住址、电子邮箱等
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.
维护者与义务
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.
适用范围
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.
报告与处理
如果你经历或目睹了辱骂、骚扰或其他不可接受的行为,可以致信给选定的项目维护者,目前是 Nami 和 Xenia。 他们将会审议投诉并酌情让其他维护者参与,然后妥善地、以不违背您意愿的方式予以必要的处理。
维护者有义务保密举报者信息。 维护者本身不能免于被投诉,经其他维护者决议后,可能会被暂时或永久地剥夺参与本项目的资格。
来源
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.