Code of Conduct
Relevant source files
The following files were used as context for generating this wiki page:
The Quickemu Code of Conduct establishes a framework for professional and inclusive interaction within the project's community. It serves as a pledge by members, contributors, and leaders to maintain a harassment-free environment for all participants, regardless of their background, identity, or level of experience.
This policy applies to all community spaces, including the official Discord channel, GitHub Discussions, and issue trackers. It also extends to instances where individuals officially represent the Quickemu community in public settings, such as using official email addresses or social media accounts.
Sources: CODE_OF_CONDUCT.md:3-10, CODE_OF_CONDUCT.md:46-51, CONTRIBUTING.md:5-10, README.md:21-25
Community Standards
The project defines clear expectations for behavior to ensure a healthy and diverse environment. These standards differentiate between positive contributions and unacceptable conduct.
Expected Behavior
Contributors are encouraged to demonstrate empathy and kindness, respect differing viewpoints, and provide or accept constructive feedback gracefully. A core tenet is focusing on the collective benefit of the community rather than individual interests.
Unacceptable Behavior
Behaviors that result in enforcement actions include, but are not limited to:
- Sexualized language, imagery, or unwanted advances.
- Trolling, insulting, or personal/political attacks.
- Public or private harassment.
- Doxing (publishing private information without permission).
- Inappropriate conduct in professional settings.
Sources: CODE_OF_CONDUCT.md:14-31
Enforcement and Responsibility
Community leaders are tasked with the active enforcement of these standards. They maintain the authority to moderate contributions—including comments, code commits, and wiki edits—that do not align with the established Code of Conduct.
Reporting Mechanism
Instances of unacceptable behavior can be reported directly to community leaders via the #quickemu channel on Discord. Leaders are obligated to investigate reports promptly and maintain the privacy and security of the reporter.
Enforcement Process Flow
The following diagram illustrates the workflow for handling reported violations:
The enforcement process ensures that every complaint is reviewed fairly and results in a graduated response based on the severity of the incident.
Sources: CODE_OF_CONDUCT.md:33-44, CODE_OF_CONDUCT.md:53-58
Community Impact Guidelines
Quickemu utilizes a graduated enforcement ladder, inspired by the Mozilla enforcement model, to address violations based on their impact.
| Stage | Impact Description | Consequence |
|---|---|---|
| 1. Correction | Unprofessional or unwelcome language/behavior. | Private written warning; possible request for public apology. |
| 2. Warning | Single incident or series of minor actions. | Warning with specified period of no interaction with involved parties. |
| 3. Temporary Ban | Serious or sustained inappropriate behavior. | Temporary suspension from all community interaction and communication. |
| 4. Permanent Ban | Pattern of violation, harassment, or disparagement of classes. | Permanent removal from all public interaction within the community. |
Sources: CODE_OF_CONDUCT.md:60-93
Integration with Development Workflows
The Code of Conduct is intrinsically linked to the project's technical contribution guidelines. Compliance with professional standards is a prerequisite for participating in the development lifecycle.
Contribution Requirements
- Pull Requests: Contributors must follow specific guidelines, including using Conventional Commits for PR titles and messages.
- Documentation: Updates to the README or Wiki are expected to adhere to the same standards of clarity and professionalism.
- Social Interactions: Participation in Quickemu Discussions and answering user questions is governed by the core conduct pledge.
The relationship between technical linting (e.g., shellcheck) and social moderation ensures both code quality and community health.
Sources: AGENTS.md:46-59, AGENTS.md:73-82, CONTRIBUTING.md:5-15
Security and Vulnerability Reporting
While the Code of Conduct covers social behavior, the SECURITY.md file outlines the conduct expected regarding technical vulnerabilities. Reports are handled on a best-efforts basis as the project is a "spare-time hobby project."
- Reporting: Vulnerabilities should be filed as issues using the "Report a vulnerability" template.
- Supported Versions: Security updates are currently focused on the 4.9.x branch.
Sources: SECURITY.md:1-18
Summary
The Quickemu Code of Conduct is a foundational document adapted from the Contributor Covenant 2.0. It bridges the gap between technical excellence (ensured by tools like shellcheck and CI workflows) and community sustainability by providing clear behavioral expectations and a transparent enforcement ladder. Adherence to these guidelines is mandatory for all individuals interacting with the project's repositories and communication channels.
Sources: CODE_OF_CONDUCT.md:95-101, AGENTS.md:31-36